From: Purva Yeshi <purvayeshi550@gmail.com>
To: corbet@lwn.net
Cc: skhan@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Move "debugging" section to the top in index.rst
Date: Tue, 4 Feb 2025 18:56:14 +0530 [thread overview]
Message-ID: <719aa4cf-15d2-4e4b-8f40-cb6f5958120e@gmail.com> (raw)
In-Reply-To: <20250203195323.13012-1-purvayeshi550@gmail.com>
On 04/02/25 01:23, Purva Yeshi wrote:
> 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
> timerlat-tracer
Apologies for not including all the relevant recipients in this patch
submission. I forgot to run the get_maintainer.pl script, but now I am
sending the patch again to the correct recipients.
Best Regards,
Purva Yeshi
next prev parent reply other threads:[~2025-02-04 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 19:53 [PATCH] docs: Move "debugging" section to the top in index.rst Purva Yeshi
2025-02-04 13:26 ` Purva Yeshi [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-04 13:36 Purva Yeshi
2025-02-04 16:39 ` Jonathan Corbet
2025-02-05 13:31 ` 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=719aa4cf-15d2-4e4b-8f40-cb6f5958120e@gmail.com \
--to=purvayeshi550@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox