public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH i2c-tools] i2cget: add mode character for SMBus block read to manpage
Date: Wed, 30 Mar 2022 18:56:06 +0200	[thread overview]
Message-ID: <20220330185606.0d6d0e94@endymion.delvare> (raw)
In-Reply-To: <20220330102028.36187-1-wsa+renesas@sang-engineering.com>

On Wed, 30 Mar 2022 12:20:28 +0200, Wolfram Sang wrote:
> The text was updated, but the mode character was forgotten.
> 
> Fixes: 789af53 ("i2cget: Add support for SMBus block read")
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>  tools/i2cget.8 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/i2cget.8 b/tools/i2cget.8
> index 83c6f7d..a836341 100644
> --- a/tools/i2cget.8
> +++ b/tools/i2cget.8
> @@ -49,7 +49,7 @@ an integer between 0x00 and 0xFF. If omitted, the currently active register
>  will be read (if that makes sense for the considered chip).
>  .PP
>  The \fImode\fR parameter, if specified, is one of the letters \fBb\fP,
> -\fBw\fP, \fBc\fP, or \fBi\fP, corresponding to a read byte data, a read
> +\fBw\fP, \fBc\fP, \fBs\fP, or \fBi\fP, corresponding to a read byte data, a read
>  word data, a write byte/read byte, an SMBus block read, or an I2C block read
>  transaction, respectively. A \fBp\fP can also be appended to the \fImode\fR
>  parameter to enable PEC, except for I2C block transactions. If the \fImode\fR

That's odd, but indeed it was forgotten. Thanks for noticing.

Reviewed-by: Jean Delvare <jdelvare@suse.de>

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2022-03-30 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 10:20 [PATCH i2c-tools] i2cget: add mode character for SMBus block read to manpage Wolfram Sang
2022-03-30 16:56 ` Jean Delvare [this message]
2022-03-30 17:25 ` Wolfram Sang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220330185606.0d6d0e94@endymion.delvare \
    --to=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox