Re: A microscopic doc update re. ios_dump_bytes()

[Jose E. Marchesi]

Hi Martin.

This is OK for master.
Thanks!

> Hello folks,
>
> I suggest the attached little doc update re ios_dump_bytes()
>
> Cheers,
> Martin
>
> diff --git a/doc/poke.texi b/doc/poke.texi
> index c9b89b20..d676b83f 100644
> --- a/doc/poke.texi
> +++ b/doc/poke.texi
> @@ -7968,6 +7968,7 @@ It has the following prototype:
>  fun ios_dump_bytes = (int<32> @var{ios},
>                        offset<uint<64>,b> @var{from},
>                        offset<uint<64>,b> @var{size},
> +                      any @var{val} = -1,
>                        offset<uint<64>, b> @var{group_by} = 2#B,
>                        int<32> @var{cluster_by} = 8,
>                        int<32> @var{ruler} = 0,
> @@ -7985,6 +7986,12 @@ is truncated to bytes.
>  @var{size} is an offset specifying the amount of bytes to dump.  The
>  offset is rounded up to the next byte.
>
> +@var{val} Instead of an explicit @code{from+size} range, a mapped value
> +can be specified using the @code{val} argument.  In this case, @code{dump}
> +will show the bytes corresponding to the given value, with visual
> +indications on what bytes correspond to what element contained in the
> +value.
> +
>  @var{group_by} determines how the bytes are grouped together in the
>  output.  Defaults to two bytes.