All of lore.kernel.org
 help / color / mirror / Atom feed
From: Purva Yeshi <purvayeshi550@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>,
	rostedt@goodmis.org, mhiramat@kernel.org
Cc: skhan@linuxfoundation.org, mathieu.desnoyers@efficios.com,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: Move "debugging" section to the top in index.rst
Date: Wed, 5 Feb 2025 19:01:15 +0530	[thread overview]
Message-ID: <ffe61212-1b2c-4db2-9e7b-e50748075495@gmail.com> (raw)
In-Reply-To: <87bjvhhdf2.fsf@trenco.lwn.net>

On 04/02/25 22:09, Jonathan Corbet wrote:
> Purva Yeshi <purvayeshi550@gmail.com> writes:
> 
>> Move the "debugging" entry to the top in Documentation/trace/index.rst.
>> Turn index.rst into a good starting point for people wanting to learn
>> about tracing. Make it the first document users see, as it serves as a
>> tracing tutorial
>>
>> Signed-off-by: Purva Yeshi <purvayeshi550@gmail.com>
>> ---
>>   Documentation/trace/index.rst | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/trace/index.rst b/Documentation/trace/index.rst
>> index 2c991dc96ace..f3d235c8438b 100644
>> --- a/Documentation/trace/index.rst
>> +++ b/Documentation/trace/index.rst
>> @@ -5,6 +5,7 @@ Linux Tracing Technologies
>>   .. toctree::
>>      :maxdepth: 2
>>   
>> +   debugging
>>      ftrace-design
>>      tracepoint-analysis
>>      ftrace
>> @@ -24,7 +25,6 @@ Linux Tracing Technologies
>>      histogram
>>      histogram-design
>>      boottime-trace
>> -   debugging
>>      hwlat_detector
>>      osnoise-tracer
> 
> So I totally approve of improving our index.rst files.  Without some
> occasional maintenance, they become unorganized dumping grounds, and
> Documentation/trace appears to be no exception.
> 
> This small change does not really help, though.  Could I please
> encourage you to consider bringing some real order to this page?  As an
> example, you could look at commit 270beb5b2aae from 6.13.
> 
> Thanks,
> 
> jon

Thanks for your feedback. I'll review commit 270beb5b2aae and work on a 
more comprehensive reorganization to bring better order to 
Documentation/trace/index.rst page.

I'll follow up with an updated patch soon.

Best regards,
Purva Yeshi

  reply	other threads:[~2025-02-05 13:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-04 13:36 [PATCH] docs: Move "debugging" section to the top in index.rst Purva Yeshi
2025-02-04 16:39 ` Jonathan Corbet
2025-02-05 13:31   ` Purva Yeshi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-03 19:53 Purva Yeshi
2025-02-04 13:26 ` Purva Yeshi

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=ffe61212-1b2c-4db2-9e7b-e50748075495@gmail.com \
    --to=purvayeshi550@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=skhan@linuxfoundation.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.