From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
William Raezer <wraezer@gmail.com>,
linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, corbet@lwn.net
Subject: Re: [PATCH] Documentation: Add a source tree map overview
Date: Mon, 2 Jun 2025 08:26:49 +0700 [thread overview]
Message-ID: <aDz92QNc3ZSVkdx3@archie.me> (raw)
In-Reply-To: <f882f6d9-c914-48af-97b7-0aad6d995819@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 2231 bytes --]
On Sun, Jun 01, 2025 at 09:50:14AM -0700, Randy Dunlap wrote:
> Hi,
>
> On 6/1/25 9:22 AM, William Raezer wrote:
> > Hello,
> >
>
> Please wrap email lines at around 72-75 characters each.
>
> > My name is William Raezer, and this is my first contribution to the Linux kernel. I'm submitting a simple but hopefully helpful addition: a high-level map of the Linux kernel source tree as a new document in `Documentation/source-map.rst`.
>
> This looks somewhat useful, although I was expecting more of a graphic presentation
> of the tree structure. But that would cause trouble with the role of each subdirectory.
> (and one can always use `tree` for that)
I was expecting tree output either.
>
> > As someone beginning to explore the internals of the Linux kernel, I noticed that while there is some documentation available that describes the subsystems in principle, there's no centralized overview of the source tree structure itself. This patch adds a basic source map that describes the role of each top-level directory in the kernel source.
> >
> > The goal is to assist both myself and others in navigating the codebase, especially new contributors who may be overwhelmed by the kernel's size and complexity. As a follow-up, I plan to add subsystem-level maps for key directories such as `kernel/`, `mm/`, and `fs/`.
> >
> > I hope this addition is seen as a positive and useful step, and I’m open to feedback or suggestions to improve it.
>
> Patches should generally be inline as email text, not as attachments.
> This is up to the maintainer to decide about...
> and gmail is not good as maintaining whitespace in emails.
> (I don't see any whitespace problems in the current patch.)
tl;dr: see Documentation/process/submitting-patches.rst.
>
> I get a warning when building with this patch applied:
>
> Documentation/source-map.rst: WARNING: document isn't included in any toctree [toc.not_included]
make htmldocs.
>
> Also, when I look at source-map.html with a web browser, no parts of
> the source-map are shown. (tested with multiple browsers)
Do you mean toctree in the sidebar?
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-06-02 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-01 16:22 William Raezer
2025-06-01 16:50 ` Randy Dunlap
2025-06-02 1:26 ` Bagas Sanjaya [this message]
2025-06-02 2:49 ` Randy Dunlap
2025-06-02 10:28 ` Bagas Sanjaya
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=aDz92QNc3ZSVkdx3@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=wraezer@gmail.com \
/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®