From: Manuel Ebner <manuelebnerli@mailbox.org>
To: Randy Dunlap <rdunlap@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Add category of subsystem-apis
Date: Fri, 06 Nov 2026 12:52:31 +0100 [thread overview]
Message-ID: <cc36e81bf914e1ba3d641d2fe5aa38c52a275ece.camel@mailbox.org> (raw)
In-Reply-To: <43787755-f0ef-4338-b0d6-fcffcdfcc402@infradead.org>
Hi Randy,
On Thu, 2026-11-05 at 14:01 -0800, Randy Dunlap wrote:
> On 11/5/26 10:15 AM, Manuel Ebner wrote:
> > Add Bus and Communication category to reduce number of items in
> > 'Other subsystems'.
> >
> > Signed-off-by: Manuel Ebner <manuelebnerli@mailbox.org>
> driver-api/index.html
> This LGTM but at first I was wondering why I2C is listed here but I3C
> is not. I3C is listed under driver-api/index.html. So are some other
> buses.
I think the actual reason is: There is Documentation/i2c/
but no Documentation/i3c/ . subsystem-apis.rst links to Documentation/<name>/index.rst ,
core-api/index.rst links to Documentation/core-api/<name>.rst .
however there is driver-api/i2c.rst and driver-api/i3c/index.rst.
Thats why Documentation/driver-api/index.rst has this:
> Bus-level documentation
> ...
> I3C subsystem
> ...
> Subsystem-specific APIs
> ...
> I2C and SMBus Subsystem
The structure is weird.
driver-api/index's justification is clearly stated, subsystem-apis's isn't.
What is it?
> That is a little confusing to me. ISTM that we need so *not* have
> 2 places listing bus documentation...
I'm not sure about that. If the files serve to different people/roles both
should be kept, adapted and refined.
> Anyway, this is a good start on that. It could be merged as is.
>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> Tested-by: Randy Dunlap <rdunlap@infradead.org>
Thanks
Manuel
>
> > ---
> > Documentation/subsystem-apis.rst | 21 ++++++++++++++-------
> > 1 file changed, 14 insertions(+), 7 deletions(-)
> >
> > diff --git a/Documentation/subsystem-apis.rst b/Documentation/subsystem-apis.rst
> > index b1ad48bb40..4e886897d3 100644
> > --- a/Documentation/subsystem-apis.rst
> > +++ b/Documentation/subsystem-apis.rst
> > @@ -24,6 +24,20 @@ Core subsystems
> > timers/index
> > locking/index
> >
> > +Bus and Communication interfaces
> > +--------------------------------
> > +
> > +.. toctree::
> > + :maxdepth: 1
> > +
> > + i2c/index
> > + pcmcia/index
> > + spi/index
> > + w1/index
> > + usb/index
> > + PCI/index
> > + peci/index
> > +
> > Human interfaces
> > ----------------
> >
> > @@ -72,11 +86,7 @@ Other subsystems
> > cpu-freq/index
> > edac/index
> > fpga/index
> > - i2c/index
> > iio/index
> > - pcmcia/index
> > - spi/index
> > - w1/index
> > watchdog/index
> > virt/index
> > hwmon/index
> > @@ -84,9 +94,6 @@ Other subsystems
> > security/index
> > crypto/index
> > bpf/index
> > - usb/index
> > - PCI/index
> > misc-devices/index
> > - peci/index
> > wmi/index
> > tee/index
prev parent reply other threads:[~2026-11-06 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 18:15 Manuel Ebner
2026-11-05 22:01 ` Randy Dunlap
2026-11-06 11:52 ` Manuel Ebner [this message]
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=cc36e81bf914e1ba3d641d2fe5aa38c52a275ece.camel@mailbox.org \
--to=manuelebnerli@mailbox.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®