From: Tejun Heo <tj@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Documentation" <linux-doc@vger.kernel.org>,
"Linux cgroups" <cgroups@vger.kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH v4] Documentation: cgroup-v2: Sync manual toctree
Date: Fri, 19 Sep 2025 06:39:22 -1000 [thread overview]
Message-ID: <aM2HOklfVET3yF_e@slm.duckdns.org> (raw)
In-Reply-To: <20250919074347.33465-2-bagasdotme@gmail.com>
On Fri, Sep 19, 2025 at 02:43:48PM +0700, Bagas Sanjaya wrote:
> Manually-arranged toctree comment in cgroup v2 documentation is a rather
> out-of-sync with actual contents: a few sections are missing and/or
> named differently.
>
> Sync the toctree.
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Applied to cgroup/for-6.18.
Thanks.
--
tejun
prev parent reply other threads:[~2025-09-19 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 7:43 [PATCH v4] Documentation: cgroup-v2: Sync manual toctree Bagas Sanjaya
2025-09-19 7:56 ` Michal Koutný
2025-09-19 16:39 ` Tejun Heo [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=aM2HOklfVET3yF_e@slm.duckdns.org \
--to=tj@kernel.org \
--cc=bagasdotme@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.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