From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: linux-kernel@vger.kernel.org, Tejun Heo <tj@kernel.org>,
Luiz Capitulino <lcapitulino@redhat.com>,
Chao Peng <chao.p.peng@linux.intel.com>,
Vikas Shivappa <vikas.shivappa@intel.com>
Subject: Re: [PATCH] cgroups: move cpuset specific checks from generic code to cpuset_can_attach
Date: Thu, 26 Nov 2015 05:09:27 -0700 [thread overview]
Message-ID: <1448539767.7954.214.camel@gmail.com> (raw)
In-Reply-To: <20151125220117.GA990@amt.cnet>
On Wed, 2015-11-25 at 20:01 -0200, Marcelo Tosatti wrote:
> Move PF_NO_SETAFFINITY check to cpuset cgroups, where it belongs.
But you took the kthreadd check with it.
-Mike
next prev parent reply other threads:[~2015-11-26 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 22:01 [PATCH] cgroups: move cpuset specific checks from generic code to cpuset_can_attach Marcelo Tosatti
2015-11-26 8:00 ` Chao Peng
2015-11-26 12:09 ` Mike Galbraith [this message]
2015-11-26 22:32 ` [PATCH] cgroups: move cpuset specific checks from generic code to cpuset_can_attach (v2) Marcelo Tosatti
2015-11-26 23:42 ` Mike Galbraith
2015-12-01 16:49 ` Tejun Heo
2015-12-02 6:21 ` Mike Galbraith
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=1448539767.7954.214.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=chao.p.peng@linux.intel.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=tj@kernel.org \
--cc=vikas.shivappa@intel.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