linux-kernel - Re: linux-next: manual merge of the xen tree with Linus' tree

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

Message-ID: <4CEAD0BC.9020407@goop.org>
Date:	Mon, 22 Nov 2010 12:21:16 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Jens Axboe <axboe@...nel.dk>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Xen Devel <Xen-devel@...ts.xensource.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Christoph Hellwig <hch@....de>
Subject: Re: linux-next: manual merge of the xen tree with Linus' tree

On 11/22/2010 12:17 PM, Jens Axboe wrote:
> I'll drop that because you should be seeing those changes come via Jens.
>>> Yep, since Linus pulled the last batch, for-linus now has the next bits
>>> (which include the xen barrier set).
>> These don't seem to be in -rc3.  Did they get dropped on the ground
>> somewhere?
> No, they are in for-linus as written above. Just not shipped off yet,
> will be soon.

No problem, I was just following up on everything outstanding for upstream.

Thanks,
    J

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