linux-kernel - Re: [VOYAGER] fix build broken by shift to smp

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4648B28A.5000800@goop.org>
Date:	Mon, 14 May 2007 12:03:38 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	James Bottomley <James.Bottomley@...senPartnership.com>
CC:	Andrew Morton <akpm@...l.org>, Linus Torvalds <torvalds@...l.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Andi Kleen <ak@...e.de>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [VOYAGER] fix build broken by shift to smp_ops

James Bottomley wrote:
> No, I'm proposing this for 2.6.22-rc1 ... Andi has already said he won't
> push the smp consolidation patch for 2.6.22.
>
> Without this patch, voyager won't even build, since the smp_ops broke
> it, so it needs to be fixed *now*.
>   

Sure, I suppose.  But given that the patch which fixes this is a simple
no-functional-changes code-motion patch, it seems odd to not use it in
favour of putting in a big chunk of duplicated code.

    J

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