From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: xen-pciback upstreaming [was Re: Xen patches merged to upstream Linux 2.6.36, plans for 2.6.37?] Date: Thu, 26 May 2011 08:44:13 -0400 Message-ID: <20110526124413.GD3386@dumpdata.com> References: <20100815160904.GM2804@reaktio.net> <20110526111814.GA14173@entuzijast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20110526111814.GA14173@entuzijast.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: Josip Rodin Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Thu, May 26, 2011 at 01:18:14PM +0200, Josip Rodin wrote: > On Sun, Aug 15, 2010 at 07:09:04PM +0300, Pasi K=E4rkk=E4inen wrote: > > What are the plans for 2.6.37 merge window? I believe at least: > > - Xen PCI frontend > >=20 > > Others? I'm going to update the XenParavirtOps and XenKernelFeatures = wiki pages.. >=20 > I happened to notice this message again :) Now the Wiki says xen-pcibac= k is > queued for this merge window... but where? It doesn't seem to be in mai= nline > git yet, or in jbarnes/pci-2.6.git. I see Konrad recently prepared > stable/xen-blkback-v3.3 in his git tree. The latest LKML discussion wit= h .. which got accepted yesterday in Linus's tree. > Jesse Barnes from late April doesn't indicate any substantial oppositio= n, > but it does seem like it might still be pending a non-cursory review...= ? Yup. I think I need to poke somebody to review it.