[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1006011005550.3637@i5.linux-foundation.org>
Date: Tue, 1 Jun 2010 10:07:19 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Tony Luck <tony.luck@...il.com>
cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Jack Steiner <steiner@....com>,
Lee Schermerhorn <lee.schermerhorn@...com>
Subject: Re: linux-next: build failure in Linus' tree
On Tue, 1 Jun 2010, Tony Luck wrote:
> On Sat, May 29, 2010 at 5:43 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > So, is it reasonable for me to ask you to revert commit
> > 0ac0c0d0f837c499afd02a802f9cf52d3027fa3b ("cpusets: randomize node rotor
> > used in cpuset_mem_spread_node()")? Reverting it won't break ia64 (since
> > their fix was to just add code that would then be unreferenced).
>
> If that's the way you go - then just revert commit
> 4ec37de89d8c758ee8115e0e64b3f994910789ee
> too. I only put that in to get the ia64 build working
> when 0ac0c0d went upstream.
I did. See commit b3f2f6cd1ff935ecac9a5346904b899d7af689fe.
Although I left the non-__node_random parts, which seemed to be an
independent compile fix.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists