public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Roman Gushchin <guro@fb.com>
Cc: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	linux-man <linux-man@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>,
	"open list:CONTROL GROUP (CGROUP)" <cgroups@vger.kernel.org>
Subject: Re: cgroups(7): documenting /sys/kernel/cgroup files
Date: Wed, 10 Jan 2018 09:45:22 -0800	[thread overview]
Message-ID: <20180110174522.GJ3668920@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20180110124407.GA26913@castle.DHCP.thefacebook.com>

On Wed, Jan 10, 2018 at 04:44:14AM -0800, Roman Gushchin wrote:
> From fdf19edb6e9594e48e89d4510767b9eb6ca2d9dd Mon Sep 17 00:00:00 2001
> From: Roman Gushchin <guro@fb.com>
> Date: Wed, 10 Jan 2018 04:35:12 -0800
> Subject: [PATCH] cgroup: make cgroup.threads delegatable
> 
> Make cgroup.threads file delegatable.
> The behavior of cgroup.threads should follow the behavior of cgroup.procs.
> 
> Signed-off-by: Roman Gushchin <guro@fb.com>
> Discovered-by: Michael Kerrisk <mtk.manpages@gmail.com>
> Cc: Tejun Heo <tj@kernel.org>

Applied to cgroup/for-4.15-fixes.

Thanks.

-- 
tejun

      parent reply	other threads:[~2018-01-10 17:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 21:11 cgroups(7): documenting /sys/kernel/cgroup files Michael Kerrisk (man-pages)
2018-01-09 11:28 ` Roman Gushchin
2018-01-09 18:52   ` Michael Kerrisk (man-pages)
2018-01-10  4:23 ` Michael Kerrisk (man-pages)
2018-01-10 12:44   ` Roman Gushchin
2018-01-10 14:02     ` Tejun Heo
2018-01-10 14:32       ` Roman Gushchin
2018-01-10 17:31       ` Michael Kerrisk (man-pages)
2018-01-10 17:33         ` Tejun Heo
2018-01-10 17:39           ` Tejun Heo
2018-01-10 17:44       ` Tejun Heo
2018-01-10 19:14         ` Michael Kerrisk (man-pages)
2018-01-10 17:45     ` 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=20180110174522.GJ3668920@devbig577.frc2.facebook.com \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=guro@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=serge@hallyn.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