From: Tejun Heo <tj@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Li Zefan <lizefan@huawei.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (cgroup tree related)
Date: Wed, 20 Mar 2013 07:51:35 -0700 [thread overview]
Message-ID: <20130320145135.GV3042@htj.dyndns.org> (raw)
In-Reply-To: <20130320154328.4b164061f7a58af5fb3f62e4@canb.auug.org.au>
On Wed, Mar 20, 2013 at 03:43:28PM +1100, Stephen Rothwell wrote:
> It has returned today. Please be more careful.
>
> In file included from include/linux/memcontrol.h:22:0,
> from include/linux/swap.h:8,
> from include/linux/suspend.h:4,
> from arch/powerpc/kernel/asm-offsets.c:24:
> include/linux/cgroup.h:742:13: warning: 'struct cgroupstats' declared inside parameter list [enabled by default]
> include/linux/cgroup.h:742:13: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
>
> I have reverted commit c2c9ad164fa3 ("cgroup: remove unneeded includes
> from cgroup.h") for today.
Oops, my bad. I mistakenly reverted the original commit from
for-next, not for-3.10 and got confused after applying more patches on
top. Fixed up now.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-03-20 14:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 5:12 linux-next: build failure after merge of the final tree (cgroup tree related) Stephen Rothwell
2013-03-13 6:33 ` Li Zefan
2013-03-13 6:33 ` Li Zefan
2013-03-20 4:43 ` Stephen Rothwell
2013-03-20 4:43 ` Stephen Rothwell
2013-03-20 14:51 ` Tejun Heo [this message]
2013-03-20 22:09 ` Stephen Rothwell
2013-03-20 22:11 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2014-02-12 5:25 Stephen Rothwell
2014-02-12 6:39 ` Tejun Heo
2014-02-12 10:47 ` Stephen Rothwell
2014-02-12 14:27 ` Tejun Heo
2014-02-12 20:36 ` Sam Ravnborg
2014-02-12 21:15 ` 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=20130320145135.GV3042@htj.dyndns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.