linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: 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: Sun, 1 Jun 2025 09:50:14 -0700	[thread overview]
Message-ID: <f882f6d9-c914-48af-97b7-0aad6d995819@infradead.org> (raw)
In-Reply-To: <CAKg96b=n1pZi4FUBqe+puUJo9ndRfU8npvo9w6fE6Enshe73Hg@mail.gmail.com>

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)

> 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.)

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]

Also, when I look at source-map.html with a web browser, no parts of
the source-map are shown. (tested with multiple browsers)

Thanks.
-- 
~Randy


  reply	other threads:[~2025-06-01 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-01 16:22 [PATCH] Documentation: Add a source tree map overview William Raezer
2025-06-01 16:50 ` Randy Dunlap [this message]
2025-06-02  1:26   ` Bagas Sanjaya
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=f882f6d9-c914-48af-97b7-0aad6d995819@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).