From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: upstream merge status for 2.6.35, .36? Date: Mon, 07 Jun 2010 09:47:34 -0700 Message-ID: <4C0D22A6.8040400@goop.org> References: <20100604223929.GA8819@orion.carnet.hr> <4C099836.1050903@goop.org> <20100607074811.GV17817@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100607074811.GV17817@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com, Josip Rodin , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org On 06/07/2010 12:48 AM, Pasi K=E4rkk=E4inen wrote: > On Fri, Jun 04, 2010 at 05:20:06PM -0700, Jeremy Fitzhardinge wrote: > =20 >> On 06/04/2010 03:39 PM, Josip Rodin wrote: >> =20 >>> What about the future? I saw Konrad's applied his swiotlb tree with t= he >>> right acks for inclusion into linux-next, so that looks like it's pla= nned >>> to be ready to go in when the .36 merge window opens, right? >>> =20 >>> =20 >> Yes, and I'm hoping we can get pcifront and pvhvm lined up for .36; wi= th >> those in place, its a short jump to full dom0 functionality (which, no >> promises, might also get into .36 on their tails). >> >> =20 > swiotlb seems to be in linux-next now.. Congratulations! > =20 Yes, indeed. It has been epic work on Konrad's part. J