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: Windows password security audit tool. GUI, reports in PDF.

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

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

Andrew Morton wrote:
> This is getting comical.
>
> According to my records, the patch
> voyager-fix-build-broken-by-shift-to-smp_ops.patch _is_ Jeremy's patch. 
> James forwarded it.
>
> I take it from your statement that we should merge some Jeremy-patch other
> than this Jeremy-patch?
>
> If "yes", than could Jeremy please resend the other patch(es) (I believe there
> are multiple patches involved) and then can James please test them?
>
> If "no" then I think I'll just go shopping.
>   

Maybe we should just refer to all patches by their SHA1 hashes.

I'm attaching the two I have, which build for me, and I think James has
tested as working.

(21583c0234c7cc1cd6c4f312ce7a2456086e2323  and
e8862935d0e773f12d73a9502f4bc7de06a6cedd, BTW.)

    J

View attachment "i386-common-smp.patch" of type "text/x-patch" (8834 bytes)

View attachment "i386-fix-voyager-build.patch" of type "text/x-patch" (7188 bytes)