linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Zefan <lizefan@huawei.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Tejun Heo <tj@kernel.org>,
	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, 13 Mar 2013 14:33:15 +0800	[thread overview]
Message-ID: <51401DAB.1070602@huawei.com> (raw)
In-Reply-To: <20130313161236.760c25633a4e8ea8d4847ccb@canb.auug.org.au>

On 2013/3/13 13:12, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the final tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
> 
> 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:748:13: warning: 'struct cgroupstats' declared inside parameter list [enabled by default]
> include/linux/cgroup.h:748:13: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
> cc1: all warnings being treated as errors
> 
> and many more similar.
> 
> Caused by commit c2c9ad164fa3 ("cgroup: remove unneeded includes from
> cgroup.h").
> 

Tejun has dropped this patch.

  reply	other threads:[~2013-03-13  6:33 UTC|newest]

Thread overview: 12+ 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 [this message]
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
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=51401DAB.1070602@huawei.com \
    --to=lizefan@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --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).