From: Jean Delvare <jdelvare@suse.de>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH i2c-tools 1/2] tools: i2ctransfer: consequently document -a
Date: Fri, 15 Mar 2019 13:43:45 +0100 [thread overview]
Message-ID: <20190315134345.333416b2@endymion> (raw)
In-Reply-To: <20190311223335.18586-2-wsa+renesas@sang-engineering.com>
Hi Wolfram,
On Mon, 11 Mar 2019 23:33:34 +0100, Wolfram Sang wrote:
> The text describing the address to be used did not reflect the recent
> change where some of the functionality of '-f' has been seperated into
> '-a'.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> CHANGES | 1 +
> tools/i2ctransfer.8 | 8 +++++---
> 2 files changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/CHANGES b/CHANGES
> index e2ea015..e9d46b5 100644
> --- a/CHANGES
> +++ b/CHANGES
> @@ -5,6 +5,7 @@ master
> tools: Consistently use snprintf instead of sprintf
> decode-dimms: Print SPD revision for DDR3 too
> Move SDR-specific code
> + i2ctransfer: Mention '-a' everywhere in the manpage
Not sure how "once" qualifies as "everywhere" ;-)
>
> 4.1 (2018-11-30)
> Makefile: Make STRIP, DESTDIR and PREFIX overridable
> diff --git a/tools/i2ctransfer.8 b/tools/i2ctransfer.8
> index 5d3cc27..1f8ed82 100644
> --- a/tools/i2ctransfer.8
> +++ b/tools/i2ctransfer.8
> @@ -96,10 +96,12 @@ It is parsed as an unsigned 16 bit integer, but note that the Linux Kernel appli
> specifies the 7-bit address of the chip to be accessed for this message, and is an integer.
> If omitted, reuse the previous address.
> Normally, addresses outside the range of 0x03-0x77 and addresses with a kernel driver attached to them will be blocked.
> -With
> +This can be overridden with
> +.I -a
> +(all) or
> .I -f
> -(force), all addresses can be used.
> -Be very careful when using that!
> +(force).
> +Be very careful when using these!
> 10-bit addresses are currently not supported at all.
>
> .PP
Looks good to me.
Reviewed-by: Jean Delvare <jdelvare@suse.de>
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2019-03-15 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 22:33 [PATCH i2c-tools 0/2] tools: improvements to handling restricted addresses Wolfram Sang
2019-03-11 22:33 ` [PATCH i2c-tools 1/2] tools: i2ctransfer: consequently document -a Wolfram Sang
2019-03-15 12:43 ` Jean Delvare [this message]
2019-03-17 21:23 ` Wolfram Sang
2019-04-23 21:13 ` Wolfram Sang
2019-03-11 22:33 ` [PATCH i2c-tools 2/2] tools: restrict all addresses defined by the standard Wolfram Sang
2019-03-15 13:24 ` Jean Delvare
2019-03-17 21:36 ` Wolfram Sang
2019-04-23 21:13 ` Wolfram Sang
2019-03-12 15:50 ` [PATCH i2c-tools 0/2] tools: improvements to handling restricted addresses Niklas Söderlund
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=20190315134345.333416b2@endymion \
--to=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@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