From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: linux-next: build failure after merge of the final tree (cgroup tree related)
Date: Wed, 12 Feb 2014 21:47:43 +1100 [thread overview]
Message-ID: <20140212214743.22fd2d8e1889ae69986e58aa@canb.auug.org.au> (raw)
In-Reply-To: <20140212063933.GB7984@mtj.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
Hi, Tejun,
On Wed, 12 Feb 2014 01:39:33 -0500 Tejun Heo <tj@kernel.org> wrote:
>
> On Wed, Feb 12, 2014 at 04:25:00PM +1100, Stephen Rothwell wrote:
> > Presumably caused by commit 2bd59d48ebfb ("cgroup: convert to kernfs")
> > (see the comment in commit 1ff6bbfd13ca ("arm, pm, vmpressure: add
> > missing slab.h includes")). I wonder how mane more builds are broken by
> > this :-(
>
> Dang, I was feeling pretty safe as kbuild bot was reporting build
> successes. We better fix them at any rate. David / Sam, can you
> please pick this one up?
It really needs to go into the tree with the cgroup commit so it doesn't
break there.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-12 10:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 5:25 linux-next: build failure after merge of the final tree (cgroup tree related) Stephen Rothwell
2014-02-12 6:39 ` Tejun Heo
2014-02-12 10:47 ` Stephen Rothwell [this message]
2014-02-12 14:27 ` Tejun Heo
2014-02-12 20:36 ` Sam Ravnborg
2014-02-12 21:15 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2013-03-13 5:12 Stephen Rothwell
2013-03-13 6:33 ` Li Zefan
2013-03-20 4:43 ` Stephen Rothwell
2013-03-20 14:51 ` Tejun Heo
2013-03-20 22:09 ` Stephen Rothwell
2013-03-20 22:11 ` Tejun Heo
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=20140212214743.22fd2d8e1889ae69986e58aa@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sam@ravnborg.org \
--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;
as well as URLs for NNTP newsgroup(s).