From: Bagas Sanjaya <bagasdotme@gmail.com>
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] docs: consolidate storage interfaces
Date: Tue, 30 May 2023 15:54:20 +0700 [thread overview]
Message-ID: <d1e4436e-b428-0f49-ecf1-079955aaecb2@gmail.com> (raw)
In-Reply-To: <20230529085521.2574848-1-costa.shul@redhat.com>
On 5/29/23 15:55, Costa Shulyupin wrote:
> +Storage interfaces
> +------------------
> +
> +.. toctree::
> + :maxdepth: 1
> +
> + filesystems/index
> + block/index
> + cdrom/index
> + scsi/index
> +
> **Fixme**: much more organizational work is needed here.
>
Can you also categorize below indexes (table of contents) like above?
> .. toctree::
> @@ -31,8 +42,6 @@ Human interfaces
> core-api/index
> locking/index
> accounting/index
> - block/index
> - cdrom/index
> cpu-freq/index
> fpga/index
> i2c/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
Thanks.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-05-30 8:54 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 [this message]
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
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=d1e4436e-b428-0f49-ecf1-079955aaecb2@gmail.com \
--to=bagasdotme@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.