linux-kernel - Re: linux-next: build failure in Linus' tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTinSRHyxGFKRnIlfUGbnLqIpZWLtq7ipYFH25wGW@mail.gmail.com>
Date:	Tue, 1 Jun 2010 10:04:25 -0700
From:	Tony Luck <tony.luck@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	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 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.

-Tony
--
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/