linux-kernel - Re: [git pull] x86 fixes

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: <20080507154818.5f22f8e0@ephemeral>
Date:	Wed, 7 May 2008 15:48:18 -0400
From:	Andres Salomon <dilinger@...ued.net>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Adrian Bunk <bunk@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [git pull] x86 fixes

On Wed, 7 May 2008 21:08:40 +0200 (CEST)
Thomas Gleixner <tglx@...utronix.de> wrote:

> On Wed, 7 May 2008, Andres Salomon wrote:
> > > Sorry, this should not have gone mainline. We had your patch
> > > queued (via Andrew) and it had testing failures, which we sent to
> > > you. One workaround was that build patch. When we dropped your
> > > patch we forgot to remove the workaround as well.
> > > 
> > 
> > Will it be removed, then?  I haven't seen any explanation of its
> > benefits, and Adrian's point about not catching build failures in
> > olpc_battery is valid.
> 
> Yes, it's scheduled for the next pull request. What's the state of the
> build failures of your original patch ?
> 
> Thanks,
> 	tglx


They're queued up in Andrew's tree, I believe.  You were also CC'd;
Message-ID: <20080504104756.3d7b6842@...emeral>.  It wasn't CC'd to
lkml, unfortunately.

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