linux-kernel - Re: Could you reinstate ticketlock cleanups in tip.git

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-next>] [day] [month] [year] [list]

Message-ID: <20110928063115.GA24510@elte.hu>
Date:	Wed, 28 Sep 2011 08:31:15 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>
Subject: Re: Could you reinstate ticketlock cleanups in tip.git


* Thomas Gleixner <tglx@...utronix.de> wrote:

> Hi Thomas,
> 
> Could you reinstate the ticketlock cleanup series in tip.git (I think it
> was in x86/spinlocks) from
>     git://github.com/jsgf/linux-xen.git upstream/ticketlock-cleanup
> 
> This branch is the final result of all the discussions and revisions and
> is ready for the next merge window.  It's the one that's been in
> linux-next for a couple of weeks (at least), and won't cause any
> conflicts there.
> 
> Or if you prefer I can submit it myself for next merge window.
> 
> Thanks,
>     J

I'd prefer if this went via x86/spinlocks. Could you please send a 
proper pull request with diffstat, shortlog, etc?

Thanks,

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