Thread (13 messages) flat view 13 messages, 4 authors, 2011-03-15

Re: linux-next: build failure after merge of the net tree

From: Stephen Rothwell <hidden>
Date: 2011-03-15 00:30:59
Also in: linux-next, lkml

Hi Dave,

On Mon, 14 Mar 2011 10:56:12 +0100 (CET) Thomas Gleixner [off-list ref] wrote:
On Mon, 14 Mar 2011, Stephen Rothwell wrote:
quoted
On Sun, 13 Mar 2011 22:53:12 -0700 (PDT) David Miller [off-list ref] wrote:
quoted
From: Stephen Rothwell <redacted>
Date: Mon, 14 Mar 2011 16:31:35 +1100
quoted
Maybe some config option changed ...
Perhaps GENERIC_HARDIRQS_NO_DEPRECATED?
Yep, that has been turned on for powerpc now.  I guess you will have the
same problem on sparc64 of you merge the net-next and sparc trees ...
Yeah, powerpc alone compiles with GENERIC_HARDIRQS_NO_DEPRECATED as it
does not have that notify commit.

If you add net which has that notify commit, but not the fix it
breaks. I wonder whether Dave should pick that fix into net.
So, if you merge the commit 1fb0ef31f428 ("genirq: Fix affinity notifier
fallout") from the tip tree, you will get exactly one new commit and will
fix your tree properly with no adverse effect on anyone else.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help