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: <20070514125946.0f74221c.akpm@linux-foundation.org>
Date:	Mon, 14 May 2007 12:59:46 -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 10:10:48 -0700
Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> James Bottomley wrote:
> > From: Jeremy Fitzhardinge <jeremy@...source.com>
> > Subject: [VOYAGER] fix build broken by shift to smp_ops
> >
> > This adds an smp_ops for voyager, and hooks things up appropriately.
> > This is the first baby-step to making subarch runtime switchable.
> >
> > Signed-off-by: Jeremy Fitzhardinge <jeremy@...source.com>
> >
> > Rediffed to work in the absence of the smp consolidation patch
> >   
> 
> I think Andrew is carrying that in -mm.  If you're proposing this for
> git, then we may as well pull in that patch too.
> 

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.

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