From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-i2c@vger.kernel.org,
Wolfram Sang <wsa@kernel.org>, Peter Rosin <peda@axentia.se>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] docs: i2c: i2c-topology: fix typo
Date: Tue, 23 Aug 2022 10:33:59 +0200 [thread overview]
Message-ID: <20220823103359.1462755e@booty> (raw)
In-Reply-To: <78a90d0a-e0ba-0189-aa84-4ce2952e33f3@gmail.com>
Hi Bagas,
On Mon, 22 Aug 2022 20:40:56 +0700
Bagas Sanjaya <bagasdotme@gmail.com> wrote:
> On 8/22/22 16:10, luca.ceresoli@bootlin.com wrote:
> > From: Luca Ceresoli <luca.ceresoli@bootlin.com>
> >
> > "intension" should have probably been "intention", however "intent" seems
> > even better.
> >
> > Reported-by: Bagas Sanjaya <bagasdotme@gmail.com>
> > Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
> >
>
> The typo error is introduced in [2/3], so it makes sense to squash this
> to the errored patch.
Patch 2 just reformats the text. "intension" was there before patch 2
and got unmodified. But if it is useful I can send a v3 with the typo
fix in patch 1 and the other two patches following.
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-08-23 11:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:10 [PATCH v2 0/3] docs: i2c: rework I2C documentation, part II luca.ceresoli
2022-08-22 9:10 ` [PATCH v2 1/3] docs: i2c: i2c-topology: fix incorrect heading luca.ceresoli
2022-08-23 9:19 ` Peter Rosin
2022-08-22 9:10 ` [PATCH v2 2/3] docs: i2c: i2c-topology: reorder sections more logically luca.ceresoli
2022-08-23 9:26 ` Peter Rosin
2022-08-23 21:01 ` Luca Ceresoli
2022-08-24 7:25 ` Peter Rosin
2022-08-22 9:10 ` [PATCH v2 3/3] docs: i2c: i2c-topology: fix typo luca.ceresoli
2022-08-22 13:40 ` Bagas Sanjaya
2022-08-23 8:33 ` Luca Ceresoli [this message]
2022-08-23 9:28 ` Peter Rosin
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=20220823103359.1462755e@booty \
--to=luca.ceresoli@bootlin.com \
--cc=bagasdotme@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=wsa@kernel.org \
/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.