From: David Miller <davem@davemloft.net>
To: geert@linux-m68k.org
Cc: rdunlap@xenotime.net, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
gleb@redhat.com, netdev@vger.kernel.org, glommer@parallels.com
Subject: Re: linux-next: Tree for Jan 25 (net/sock.h, jump_label, memcg)
Date: Thu, 26 Jan 2012 13:43:33 -0500 (EST) [thread overview]
Message-ID: <20120126.134333.31948964659222759.davem@davemloft.net> (raw)
In-Reply-To: <CAMuHMdWp1wEHqPXNs+kaMYpomJnfbZPJjRk5GVFCuCL4Q5zK7g@mail.gmail.com>
From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: Thu, 26 Jan 2012 18:18:28 +0100
> On Wed, Jan 25, 2012 at 20:07, Randy Dunlap <rdunlap@xenotime.net> wrote:
>> back to net/sock.h and jump_label:
>>
>> (on i386:)
>>
>> /next/linux-next-20120125/include/net/sock.h:953:2: error: implicit declaration of function 'static_branch'
>> /next/linux-next-20120125/include/linux/jump_label.h:43:29: error: conflicting types for 'static_branch'
>>
>> Full randconfig file is attached.
>
> Without having to add randomness, also in m68k/allmodconfig, now in Linus'
> tree :-(
> http://kisskb.ellerman.id.au/kisskb/buildresult/5491860/
Glauber are you actually going to fix this or are you going to ignore
this bug report for another couple days?!?!
Frankly, I'm so sick and tired of all of these socket mem cgroup
regressions, this is way out of control and every "fix" seems to add
more build or runtime regressions.
Glauber, this has to stabilize soon or I will revert every single one
of your changes, and it will take a nuclear war and a multi-month
audit of your code to get those changes into the tree again.
next prev parent reply other threads:[~2012-01-26 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 3:19 linux-next: Tree for Jan 25 Stephen Rothwell
2012-01-25 19:07 ` linux-next: Tree for Jan 25 (net/sock.h, jump_label, memcg) Randy Dunlap
2012-01-26 17:18 ` Geert Uytterhoeven
2012-01-26 18:43 ` David Miller [this message]
2012-01-26 20:31 ` Glauber Costa
2012-01-26 21:46 ` Stephen Rothwell
2012-01-26 21:47 ` Glauber Costa
2012-01-25 21:52 ` [PATCH -next] uwb & wusb: fix kconfig error Randy Dunlap
2012-01-27 23:47 ` [PATCH -next] uwb & wusb & usb wireless controllers: fix kconfig error & build errors Randy Dunlap
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=20120126.134333.31948964659222759.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=gleb@redhat.com \
--cc=glommer@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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 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).