linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Costa Shulyupin <costa.shul@redhat.com>, linux-doc@vger.kernel.org
Cc: Costa Shulyupin <costa.shul@redhat.com>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] docs: consolidate peripheral interfaces
Date: Fri, 21 Jul 2023 14:58:05 -0600	[thread overview]
Message-ID: <874jlxc78i.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230715165759.74901-1-costa.shul@redhat.com>

Costa Shulyupin <costa.shul@redhat.com> writes:

> to make the page more organized as requested
>
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
> ---
>  Documentation/subsystem-apis.rst | 15 +++++++++++----
>  1 file changed, 11 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/subsystem-apis.rst b/Documentation/subsystem-apis.rst
> index 90a0535a932a..7b086c89e2be 100644
> --- a/Documentation/subsystem-apis.rst
> +++ b/Documentation/subsystem-apis.rst
> @@ -48,6 +48,17 @@ Networking interfaces
>     isdn/index
>     mhi/index
>  
> +Peripheral interfaces
> +----------------------
> +
> +.. toctree::
> +   :maxdepth: 1
> +
> +   usb/index
> +   PCI/index
> +   hwmon/index
> +   leds/index
> +
>  Storage interfaces
>  ------------------
>  
> @@ -70,19 +81,15 @@ 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

So this one seems a bit less well thought out.  How are you defining
"peripheral interface"?  How is it that PCI qualifies but, say, PCMCIA
does not?  In a real sense, most of our interfaces deal with peripherals
in one way or another.

Were you thinking maybe of "bus interfaces"?  If so, a somewhat
different selection would be indicated.

Thanks,

jon

  reply	other threads:[~2023-07-21 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-15 16:57 [PATCH 2/3] docs: consolidate peripheral interfaces Costa Shulyupin
2023-07-21 20:58 ` Jonathan Corbet [this message]
2023-07-22 11:32   ` [PATCH v2 " Costa Shulyupin
2023-07-24 16:16     ` 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=874jlxc78i.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=costa.shul@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).