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]

Date:	Mon, 14 May 2007 13:37:45 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	James Bottomley <James.Bottomley@...senPartnership.com>,
	Linus Torvalds <torvalds@...ux-foundation.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

On Mon, 14 May 2007 13:02:42 -0700
Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> Andrew Morton wrote:
> > Does "that" have name?  I can find no patch in -mm which appears to have
> > anything to do with SMP consolidation, and this patch applies cleanly to
> > the current -mm lineup.
> >   
> Sorry, I thought you'd picked this up:
> 
> 
> Subject: i386: move common parts of smp into their own file
> 
> Several parts of kernel/smp.c and smpboot.c are generally useful for
> other subarchitectures and paravirt_ops implementations, so make them
> available for reuse.

Confused.  This patch conflicts a lot with James's one (which I named
voyager-fix-build-broken-by-shift-to-smp_ops.patch).

If your "i386: move common parts of smp into their own file" also fixes
Voyager and is preferred then cool, but a) the changelog should tell us
that and b) could James please test it?

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