From: Peter Rosin <peda@axentia.se>
To: luca.ceresoli@bootlin.com, linux-doc@vger.kernel.org,
linux-i2c@vger.kernel.org
Cc: Wolfram Sang <wsa@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] docs: i2c: i2c-topology: fix incorrect heading
Date: Tue, 23 Aug 2022 11:19:45 +0200 [thread overview]
Message-ID: <66c525ff-1835-b4c7-c7ee-469060826ad6@axentia.se> (raw)
In-Reply-To: <20220822091050.47099-2-luca.ceresoli@bootlin.com>
Hi!
[sorry for not responding to v1]
2022-08-22 at 11:10, luca.ceresoli@bootlin.com wrote:
> From: Luca Ceresoli <luca.ceresoli@bootlin.com>
>
> "Etc" here was never meant to be a heading, it became one while converting
> to ReST.
>
> It would be easy to just convert it to plain text, but rather remove it and
> add an introductory text before the list that conveys the same meaning but
> with a better reading flow.
>
> Fixes: ccf988b66d69 ("docs: i2c: convert to ReST and add to driver-api bookset")
> Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Acked-by: Peter Rosin <peda@axentia.se>
Cheers,
Peter
>
> ---
>
> Changed in v2: none
> ---
> Documentation/i2c/i2c-topology.rst | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/i2c/i2c-topology.rst b/Documentation/i2c/i2c-topology.rst
> index 7cb53819778e..1b11535c8946 100644
> --- a/Documentation/i2c/i2c-topology.rst
> +++ b/Documentation/i2c/i2c-topology.rst
> @@ -5,6 +5,8 @@ I2C muxes and complex topologies
> There are a couple of reasons for building more complex I2C topologies
> than a straight-forward I2C bus with one adapter and one or more devices.
>
> +Some example use cases are:
> +
> 1. A mux may be needed on the bus to prevent address collisions.
>
> 2. The bus may be accessible from some external bus master, and arbitration
> @@ -14,9 +16,6 @@ than a straight-forward I2C bus with one adapter and one or more devices.
> from the I2C bus, at least most of the time, and sits behind a gate
> that has to be operated before the device can be accessed.
>
> -Etc
> -===
> -
> These constructs are represented as I2C adapter trees by Linux, where
> each adapter has a parent adapter (except the root adapter) and zero or
> more child adapters. The root adapter is the actual adapter that issues
next prev parent reply other threads:[~2022-08-23 11:17 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 [this message]
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
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=66c525ff-1835-b4c7-c7ee-469060826ad6@axentia.se \
--to=peda@axentia.se \
--cc=linux-doc@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--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 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).