From: Costa Shulyupin <costa.shul@redhat.com>
To: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org (open list:DOCUMENTATION),
linux-kernel@vger.kernel.org (open list)
Cc: Costa Shulyupin <costa.shul@redhat.com>
Subject: [PATCH v2 2/3] docs: consolidate peripheral interfaces
Date: Sat, 22 Jul 2023 14:32:53 +0300 [thread overview]
Message-ID: <20230722113253.1545231-1-costa.shul@redhat.com> (raw)
In-Reply-To: <874jlxc78i.fsf@meer.lwn.net>
to make page Subsystems APIs more organized as requested
Changes:
v2: added pcmcia and subtitle
Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
---
Alternative consolidation of buses look more challenging.
Here are too many buses, so them should be split again.
Many of buses are specific for only x86 or only embedded computers.
Is SCSI generic bus or storage bus?
---
Documentation/subsystem-apis.rst | 19 ++++++++++++++-----
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/Documentation/subsystem-apis.rst b/Documentation/subsystem-apis.rst
index 90a0535a932a..5ace1c434977 100644
--- a/Documentation/subsystem-apis.rst
+++ b/Documentation/subsystem-apis.rst
@@ -48,6 +48,20 @@ Networking interfaces
isdn/index
mhi/index
+Peripheral interfaces
+----------------------
+
+except specific networking and storage interfaces
+
+.. toctree::
+ :maxdepth: 1
+
+ usb/index
+ PCI/index
+ hwmon/index
+ leds/index
+ pcmcia/index
+
Storage interfaces
------------------
@@ -70,19 +84,14 @@ Storage interfaces
fpga/index
i2c/index
iio/index
- leds/index
- pcmcia/index
spi/index
w1/index
watchdog/index
virt/index
- hwmon/index
accel/index
security/index
crypto/index
bpf/index
- usb/index
- PCI/index
misc-devices/index
peci/index
wmi/index
--
2.41.0
next prev parent reply other threads:[~2023-07-22 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 16:57 [PATCH " Costa Shulyupin
2023-07-21 20:58 ` Jonathan Corbet
2023-07-22 11:32 ` Costa Shulyupin [this message]
2023-07-24 16:16 ` [PATCH v2 " Jonathan Corbet
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=20230722113253.1545231-1-costa.shul@redhat.com \
--to=costa.shul@redhat.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®