From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "Linux I2C" <linux-i2c@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Subject: Re: [PATCH i2c-tools 2/2] i2ctransfer: grammar fixes in manpage
Date: Tue, 4 Apr 2017 09:31:17 +0200 [thread overview]
Message-ID: <CAMuHMdX7JayJUD5dO_WSvtp3YuKrf3JEGd3C2YAzcgW6W0zjNg@mail.gmail.com> (raw)
In-Reply-To: <20170403173613.2238-2-wsa+renesas@sang-engineering.com>
Hi Wolfram,
On Mon, Apr 3, 2017 at 7:36 PM, Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> --- a/tools/i2ctransfer.8
> +++ b/tools/i2ctransfer.8
> @@ -74,7 +74,7 @@ This number should correspond to one of the busses listed by
> The next parameter is one or multiple
> .I desc
> blocks.
> -The number of blocks is limited by the Linux Kernel and defined in I2C_RDWR_IOCTL_MAX_MSGS (42 as of v4.10).
> +The number of blocks is limited by the Linux Kernel and defined with I2C_RDWR_IOCTL_MAX_MSGS (42 as of v4.10).
defined by?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2017-04-04 7:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 17:36 [PATCH i2c-tools 1/2] i2ctransfer: replace broken "force" handling Wolfram Sang
2017-04-03 17:36 ` [PATCH i2c-tools 2/2] i2ctransfer: grammar fixes in manpage Wolfram Sang
2017-04-04 7:31 ` Geert Uytterhoeven [this message]
2017-04-07 12:13 ` Wolfram Sang
2017-04-07 12:13 ` [PATCH i2c-tools 1/2] i2ctransfer: replace broken "force" handling 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=CAMuHMdX7JayJUD5dO_WSvtp3YuKrf3JEGd3C2YAzcgW6W0zjNg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).