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: <1179163348.3703.57.camel@mulgrave.il.steeleye.com>
Date:	Mon, 14 May 2007 12:22:28 -0500
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
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

On Mon, 2007-05-14 at 10:10 -0700, Jeremy Fitzhardinge 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.

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*.

James


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