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] docs: consolidate core subsystems
Date: Thu, 22 Jun 2023 08:35:06 -0700 [thread overview]
Message-ID: <a0e8aba6-b28f-c460-9bab-5695000727fb@infradead.org> (raw)
In-Reply-To: <20230622071004.2934698-1-costa.shul@redhat.com>
Hi--
On 6/22/23 00:10, Costa Shulyupin wrote:
> to make the page more organized as requested
>
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
> ---
> 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 b67a1b65855b..8664b05777c3 100644
> --- a/Documentation/subsystem-apis.rst
> +++ b/Documentation/subsystem-apis.rst
> @@ -10,6 +10,20 @@ is taken directly from the kernel source, with supplemental material added
> as needed (or at least as we managed to add it — probably *not* all that is
> needed).
>
> +Core subsystems
> +---------------
> +
> +.. toctree::
> + :maxdepth: 1
> +
> + core-api/index
> + driver-api/index
> + mm/index
> + power/index
> + scheduler/index
> + timers/index
> + locking/index
> +
In general I am OK with this grouping, except for 2 nits:
a. I'm not sure that locking is a subsystem (it's a core API IMO).
b. I often have trouble finding "filesystems" and I think that it should be
given a higher location in the TOC (somehow).
thanks.
--
~Randy
next prev parent reply other threads:[~2023-06-22 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 7:10 [PATCH] docs: consolidate core subsystems Costa Shulyupin
2023-06-22 15:35 ` Randy Dunlap [this message]
2023-06-22 16:57 ` Costa Shulyupin
2023-07-14 19:38 ` 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=a0e8aba6-b28f-c460-9bab-5695000727fb@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).