All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Daniel Wagner <daniel.wagner@bmw-carit.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Li Zefan <lizefan@huawei.com>,
	Neil Horman <nhorman@tuxdriver.com>
Subject: Re: linux-next: build failure after merge of the cgroup tree
Date: Fri, 14 Sep 2012 10:00:19 -0700	[thread overview]
Message-ID: <20120914170019.GA17747@google.com> (raw)
In-Reply-To: <5052D51D.3060106@bmw-carit.de>

Hello,

On Fri, Sep 14, 2012 at 08:56:29AM +0200, Daniel Wagner wrote:
> On 14.09.2012 05:17, Stephen Rothwell wrote:
> >After merging the cgroup tree, today's linux-next build (powerpc
> >ppc64_defconfig) failed like this:
> >
> >drivers/net/tun.c: In function 'tun_alloc_skb':
> >drivers/net/tun.c:589:2: error: implicit declaration of function 'sock_update_classid' [-Werror=implicit-function-declaration]
> >
> >Caused by commit 1f66c0a8833c ("cgroup: net_cls: Move sock_update_classid()
> >declaration to cls_cgroup.h").  Grep is your friend ...

My apologies.  Forgot allmod build.

> >I have used the cgroup tree from next-20120913 for today.
> 
> Obviously, it is straight forward to fix this but I do not know what
> is the preferred solution. Shall I spin an updated version of this
> patch or add a patch on top of the series?

I fixed the commit in tree.

Thanks.

-- 
tejun

  reply	other threads:[~2012-09-14 17:00 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  3:17 linux-next: build failure after merge of the cgroup tree Stephen Rothwell
2012-09-14  6:56 ` Daniel Wagner
2012-09-14 17:00   ` Tejun Heo [this message]
2012-09-14 18:32     ` Sedat Dilek
2012-09-14 18:34       ` Tejun Heo
2012-09-15  7:55         ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
2025-08-25  5:03 Stephen Rothwell
2025-08-25 18:18 ` Tejun Heo
2024-07-12  6:43 Stephen Rothwell
2024-07-12  6:51 ` Stephen Rothwell
2024-07-12 14:48   ` Jonathan Corbet
2024-07-12 16:44     ` Tejun Heo
2024-07-12 16:50       ` Tejun Heo
2023-12-07  3:38 Stephen Rothwell
2023-12-07  4:18 ` Waiman Long
2023-07-17  1:34 Stephen Rothwell
2023-07-17  6:45 ` Miaohe Lin
2022-10-31  2:23 Stephen Rothwell
2022-10-31 17:52 ` Tejun Heo
2022-09-12  6:18 Stephen Rothwell
2022-09-12  7:38 ` Peter Zijlstra
2022-09-12 18:44   ` Tejun Heo
2022-09-12 22:16     ` Tejun Heo
2022-09-15 10:46       ` Peter Zijlstra
2022-10-10 20:57 ` Stephen Rothwell
2022-10-10 20:59   ` Tejun Heo
2022-08-29  3:29 Stephen Rothwell
2021-05-11  0:51 Stephen Rothwell
2021-05-11  1:10 ` Roman Gushchin
2021-05-11  1:31   ` Tejun Heo
2021-04-22  6:31 Stephen Rothwell
2015-09-25  3:26 Stephen Rothwell
2014-02-26  6:46 Stephen Rothwell
2014-02-26 13:44 ` Tejun Heo
2013-04-29  4:04 Stephen Rothwell
2013-04-29  4:04 ` Stephen Rothwell
2013-04-29  4:04 ` Stephen Rothwell
2013-04-29 22:55 ` Tejun Heo
2013-04-29 22:55   ` Tejun Heo
2013-04-30  1:51   ` Benjamin Herrenschmidt
2013-04-30  1:51     ` Benjamin Herrenschmidt
2011-11-25  3:50 Stephen Rothwell
2011-11-27 19:33 ` 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=20120914170019.GA17747@google.com \
    --to=tj@kernel.org \
    --cc=daniel.wagner@bmw-carit.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=nhorman@tuxdriver.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.