public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kernel Tracing <linux-trace-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v2 0/2] Table of contents refactoring for tracing docs
Date: Mon, 21 Apr 2025 10:38:12 -0600	[thread overview]
Message-ID: <877c3dzczv.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250416024050.19735-1-bagasdotme@gmail.com>

Bagas Sanjaya <bagasdotme@gmail.com> writes:

> Hi,
>
> The trace toctree refactoring series [1] didn't make it through 6.15
> merge window previously, so I forwarded it targeting 6.16 via
> docs-next tree instead.
>
> Enjoy!
>
> Changes since v1 [2]:
>
>   - Remove mention of individual docs' toctree as the generated sidebar
>     toctree don't include them ([patch 1/2])
>   - Move uprobetracer to user-space tracing section (Steven, [patch 2/2])
>
> [1]: https://lore.kernel.org/linux-doc/20250318113230.24950-1-purvayeshi550@gmail.com/T/#u
> [2]: https://lore.kernel.org/linux-doc/20250415034613.21305-1-bagasdotme@gmail.com/
>
> Purva Yeshi (2):
>   Documentation: trace: Reduce toctree depth
>   Documentation: trace: Refactor toctree
>
>  Documentation/trace/index.rst | 98 +++++++++++++++++++++++++++++------
>  1 file changed, 81 insertions(+), 17 deletions(-)

Applied, thanks.

jon

      parent reply	other threads:[~2025-04-21 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16  2:40 [PATCH v2 0/2] Table of contents refactoring for tracing docs Bagas Sanjaya
2025-04-16  2:40 ` [PATCH v2 1/2] Documentation: trace: Reduce toctree depth Bagas Sanjaya
2025-04-16  2:40 ` [PATCH v2 2/2] Documentation: trace: Refactor toctree Bagas Sanjaya
2025-04-16 14:12 ` [PATCH v2 0/2] Table of contents refactoring for tracing docs Steven Rostedt
2025-04-21 16:38 ` Jonathan Corbet [this message]

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=877c3dzczv.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=bagasdotme@gmail.com \
    --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 \
    /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