From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: tj@kernel.org
Cc: lizefan@huawei.com, peterz@infradead.org, mingo@kernel.org,
keescook@chromium.org, miaox@cn.fujitsu.com,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
rientjes@google.com
Subject: Re: [PATCH v3 1/3] sched: fix confusing PFA_NO_NEW_PRIVS constant
Date: Wed, 24 Sep 2014 23:09:25 +0900 [thread overview]
Message-ID: <201409242309.HDF95877.OSVFFtQLJMOHOF@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20140924133513.GD16555@htj.dyndns.org>
Tejun Heo wrote:
> > Applied 1-3 to cgroup/for-3.17-fixes w/ the typo spotted by davidr
> > fixed.
s/happend/happened/
>
> Reverted due to build failure. Will wait for a refreshed version. :(
I can build with 1-3 patches using HEAD of linux.git. What failure did you see?
$ make kernel/seccomp.o kernel/sys.o security/apparmor/domain.o kernel/cpuset.o
next prev parent reply other threads:[~2014-09-24 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 7:44 [PATCH v3 1/3] sched: fix confusing PFA_NO_NEW_PRIVS constant Zefan Li
2014-09-23 7:44 ` [PATCH v3 2/3] sched: add macros to define bitops for task atomic flags Zefan Li
[not found] ` <542124FB.4030109-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-09-23 10:01 ` Peter Zijlstra
[not found] ` <20140923100127.GE3312-IIpfhp3q70z/8w/KjCw3T+5/BudmfyzbbVWyRVo5IupeoWH0uzbU5w@public.gmane.org>
2014-09-23 16:58 ` Kees Cook
2014-09-23 7:45 ` [PATCH v3 3/3] cpuset: PF_SPREAD_PAGE and PF_SPREAD_SLAB should be " Zefan Li
2014-09-23 22:10 ` David Rientjes
[not found] ` <alpine.DEB.2.02.1409231508590.22630-X6Q0R45D7oAcqpCFd4KODRPsWskHk0ljAL8bYrjMMd8@public.gmane.org>
2014-09-24 3:15 ` Zefan Li
[not found] ` <542124D3.9000007-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2014-09-24 13:22 ` [PATCH v3 1/3] sched: fix confusing PFA_NO_NEW_PRIVS constant Tejun Heo
[not found] ` <20140924132218.GC16555-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2014-09-24 13:35 ` Tejun Heo
2014-09-24 14:09 ` Tetsuo Handa [this message]
[not found] ` <201409242309.HDF95877.OSVFFtQLJMOHOF-JPay3/Yim36HaxMnTkn67Xf5DAMn2ifp@public.gmane.org>
2014-09-24 14:32 ` Tejun Heo
[not found] ` <20140924133513.GD16555-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2014-09-25 1:42 ` Zefan Li
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=201409242309.HDF95877.OSVFFtQLJMOHOF@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=cgroups@vger.kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=miaox@cn.fujitsu.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=tj@kernel.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