From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Vishal Chourasia" <vishalc@linux.ibm.com>,
"Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Jonathan Corbet" <corbet@lwn.net>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: cgroup: clarify controller enabling semantics
Date: Tue, 27 May 2025 17:04:29 +0700 [thread overview]
Message-ID: <aDWOLU4qjhl0ds0U@archie.me> (raw)
In-Reply-To: <20250527085335.256045-2-vishalc@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 880 bytes --]
On Tue, May 27, 2025 at 02:23:36PM +0530, Vishal Chourasia wrote:
> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
> index 1a16ce68a4d7..0e1686511c45 100644
> --- a/Documentation/admin-guide/cgroup-v2.rst
> +++ b/Documentation/admin-guide/cgroup-v2.rst
> @@ -438,8 +438,8 @@ Controlling Controllers
> Enabling and Disabling
> ~~~~~~~~~~~~~~~~~~~~~~
>
> -Each cgroup has a "cgroup.controllers" file which lists all
> -controllers available for the cgroup to enable::
> +Each cgroup has a cgroup.controllers file, which lists all the controllers
> +available for that cgroup and which can be enabled for its children.
Keep the double colon (literal code block).
>
> # cat cgroup.controllers
> cpu io memory
> --
> 2.49.0
>
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-05-27 10:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 8:53 [PATCH] Documentation: cgroup: clarify controller enabling semantics Vishal Chourasia
2025-05-27 9:58 ` Michal Koutný
2025-05-28 13:18 ` Vishal Chourasia
2025-05-28 17:05 ` Michal Koutný
2025-05-28 18:08 ` Vishal Chourasia
2025-05-28 13:31 ` Vishal Chourasia
2025-05-27 10:04 ` Bagas Sanjaya [this message]
2025-05-28 17:28 ` Vishal Chourasia
2025-05-28 15:23 ` Waiman Long
2025-05-28 15:45 ` Waiman Long
2025-05-28 17:37 ` Vishal Chourasia
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=aDWOLU4qjhl0ds0U@archie.me \
--to=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 \
--cc=tj@kernel.org \
--cc=vishalc@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).