linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Costa Shulyupin <costa.shul@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org
Cc: open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] docs: consolidate storage interfaces
Date: Sun, 18 Jun 2023 08:19:51 -0700	[thread overview]
Message-ID: <c0c44b35-b55d-6965-7103-76d9a9bf5c0d@infradead.org> (raw)
In-Reply-To: <20230618062937.481280-1-costa.shul@redhat.com>

Hi Costa,

On 6/17/23 23:29, Costa Shulyupin wrote:
> to make the page more organized as requested
> 
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
> 
> ---
> 
> Changes:
>  v4. rollback to single Storage category, add 'TCM Virtual Device'

What does the TCM Virtual Device comment refer to?

Otherwise LGTM.
Acked-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

>  v3. add Integrity, Virtualization and Miscellaneous per Bagas Sanjaya
>  v2. add Core subsystems, Networking, Peripherals and Embedded
>  v1. add Storage category
> ---
>  Documentation/subsystem-apis.rst | 17 ++++++++++++-----
>  1 file changed, 12 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/subsystem-apis.rst b/Documentation/subsystem-apis.rst
> index 55c90d5383ef..b67a1b65855b 100644
> --- a/Documentation/subsystem-apis.rst
> +++ b/Documentation/subsystem-apis.rst
> @@ -22,6 +22,18 @@ Human interfaces
>     gpu/index
>     fb/index
>  
> +Storage interfaces
> +------------------
> +
> +.. toctree::
> +   :maxdepth: 1
> +
> +   filesystems/index
> +   block/index
> +   cdrom/index
> +   scsi/index
> +   target/index
> +
>  **Fixme**: much more organizational work is needed here.
>  
>  .. toctree::
> @@ -31,8 +43,6 @@ Human interfaces
>     core-api/index
>     locking/index
>     accounting/index
> -   block/index
> -   cdrom/index
>     cpu-freq/index
>     fpga/index
>     i2c/index
> @@ -44,7 +54,6 @@ Human interfaces
>     networking/index
>     pcmcia/index
>     power/index
> -   target/index
>     timers/index
>     spi/index
>     w1/index
> @@ -54,12 +63,10 @@ Human interfaces
>     accel/index
>     security/index
>     crypto/index
> -   filesystems/index
>     mm/index
>     bpf/index
>     usb/index
>     PCI/index
> -   scsi/index
>     misc-devices/index
>     scheduler/index
>     mhi/index

-- 
~Randy

  reply	other threads:[~2023-06-18 15:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29  8:55 [PATCH] docs: consolidate storage interfaces Costa Shulyupin
2023-05-30  8:54 ` Bagas Sanjaya
2023-05-31 10:17   ` [PATCH] docs: organize subsystems Costa Shulyupin
2023-06-01  3:13     ` Bagas Sanjaya
2023-06-01 14:55       ` [PATCH v3] Documentation: subsystem-apis: Categorize remaining subsystems Costa Shulyupin
2023-06-01 16:28         ` Randy Dunlap
2023-06-02 10:08         ` Bagas Sanjaya
2023-06-02 10:19           ` Jonathan Corbet
2023-06-02 12:33             ` Bagas Sanjaya
2023-06-09  8:05         ` Jonathan Corbet
2023-06-18  6:29           ` [PATCH v4] docs: consolidate storage interfaces Costa Shulyupin
2023-06-18 15:19             ` Randy Dunlap [this message]
2023-06-18 16:09               ` Costa Shulyupin
2023-06-21 15:33             ` 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=c0c44b35-b55d-6965-7103-76d9a9bf5c0d@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=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).