linux-kernel - Re: #tj-percpu has been rebased

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:	Sat, 31 Jan 2009 14:28:28 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Tejun Heo <tj@...nel.org>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Rusty Russell <rusty@...tcorp.com.au>, x86@...nel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>, cpw@....com
Subject: Re: #tj-percpu has been rebased


* Tejun Heo <tj@...nel.org> wrote:

> Hello, again.
> 
> Please disregard the previous two rebased trees.  There has been a
> major communication misunderstanding between Ingo and me leading to
> the rebased branches.  Here is yet another, hopefully final, merged
> tree which builds on top of tip/core/percpu and took only about ten
> minutes as opposed to hours.  :-)
> 
> * Three xen fix related patches merged.  Later threes conflicted in
>   non-minor way.  Requested refresh.
> 
> * Cliff Wickman's UV flush fix patch revived and merged.
> 
> * Pull in linus#master[1].
> 
> Anyways, please pull from
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git tj-percpu
> 
> The commit ID should be da2c0b021cde94866f1e492f940aad29e8f61258.
> 
> Sorry about the mess but this one should be the safe one to post
> patches against.

Very nice - pulled into tip/core/percpu, thanks Tejun!

	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/