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]

Date:	Mon, 14 May 2007 17:27:39 -0500
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	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, 2007-05-14 at 15:00 -0700, Jeremy Fitzhardinge wrote:
> Andrew Morton wrote:
> > Well, let's get the build fix in place first and then we can feed
> > the cleanup in later on, in a more leisurely fashion?
> >   
> 
> If you like.  Are all the Voyager users standing outside your office
> with pitchforks, demanding satisfaction?

That could be arranged ...  The Xensource offices are just up the road
from Google, you know if I wanted to kill two birds with one stone.

Seriously, though, although I tolerate voyager breakage through the
merge window, I actively try to clean it up and have a working voyager
for the next release.  There's no real excuse for not fixing build
breakage.  How it's done, I don't really care.  The only blocker for the
two patch smp consolidation + voyager fix was Andi ... if he's relaxing
that, then we can go that route.

Until this is fixed, there are going to be -rc testers firing off build
failure reports, which I think we'd all like to 

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/