All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	"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: Fri, 7 Apr 2017 14:13:09 +0200	[thread overview]
Message-ID: <20170407121309.6anksmcltjgtmkex@ninjato> (raw)
In-Reply-To: <CAMuHMdX7JayJUD5dO_WSvtp3YuKrf3JEGd3C2YAzcgW6W0zjNg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

On Tue, Apr 04, 2017 at 09:31:17AM +0200, Geert Uytterhoeven wrote:
> 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?

Thanks, yes. Fixed locally and pushed out.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-04-07 12:13 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
2017-04-07 12:13     ` Wolfram Sang [this message]
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=20170407121309.6anksmcltjgtmkex@ninjato \
    --to=wsa@the-dreams.de \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.