linux-kernel - Re: [PATCH] docs: fix WARNING document not included in any toctree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87h69izs3b.fsf@trenco.lwn.net>
Date: Fri, 11 Oct 2024 07:28:40 -0600
From: Jonathan Corbet <corbet@....net>
To: Suraj Sonawane <surajsonawane0215@...il.com>, Steven Rostedt
 <rostedt@...dmis.org>
Cc: mhiramat@...nel.org, mathieu.desnoyers@...icios.com,
 linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
 linux-doc@...r.kernel.org
Subject: Re: [PATCH] docs: fix WARNING document not included in any toctree

Suraj Sonawane <surajsonawane0215@...il.com> writes:

> Can I send an updated patch with this change (moving debugging section 
> to the top)?

The patch is already applied, so no.  You can send a new patch against
docs-next if that sort of movement is warranted.

Honestly, though, just shuffling one file around only seems so useful.
What would be nice would be to turn index.rst into a good starting point
for people wanting to learn about tracing, rather than just a jumble of
files.  It needs organization into sections and some connecting text; as
an example, see the (minimal) organizational work that I did for
Documentation/process/index.rst. 

It's more work, but would certainly pay off.

Thanks,

jon