All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Josip Rodin <joy@entuzijast.net>
Cc: xen-devel@lists.xensource.com
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	[thread overview]
Message-ID: <20110526124413.GD3386@dumpdata.com> (raw)
In-Reply-To: <20110526111814.GA14173@entuzijast.net>

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ärkkäinen wrote:
> > What are the plans for 2.6.37 merge window? I believe at least:
> > - Xen PCI frontend
> > 
> > Others? I'm going to update the XenParavirtOps and XenKernelFeatures wiki pages..
> 
> I happened to notice this message again :) Now the Wiki says xen-pciback is
> queued for this merge window... but where? It doesn't seem to be in mainline
> 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 with

.. which got accepted yesterday in Linus's tree.

> Jesse Barnes from late April doesn't indicate any substantial opposition,
> 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.

      reply	other threads:[~2011-05-26 12:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 16:09 Xen patches merged to upstream Linux 2.6.36, plans for 2.6.37? Pasi Kärkkäinen
2010-08-16  5:27 ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-16  5:29 ` [Xen-devel] " Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-16 12:55   ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-16 13:04     ` Pasi Kärkkäinen
2010-08-16 16:44       ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-16 16:55         ` Pasi Kärkkäinen
2010-08-16 17:23           ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-16 23:28             ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-17  0:10               ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-17  0:43                 ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-17  5:57               ` Pasi Kärkkäinen
2010-08-18  5:26                 ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-19  1:21                   ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-19 12:55                     ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-24 11:49                       ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-24 14:30                         ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-24 15:43                         ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-24 16:28                           ` Pasi Kärkkäinen
2010-08-19  1:29                   ` [Xen-devel] " Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-18  5:28                 ` Mr. Teo En Ming (Zhang Enming) of Singapore
2010-08-16 10:42 ` Stefano Stabellini
2010-08-16 10:48   ` Pasi Kärkkäinen
2010-08-16 11:48 ` Josip Rodin
2010-08-16 16:11   ` Konrad Rzeszutek Wilk
2010-08-16 20:40     ` Josip Rodin
2011-05-26 11:18 ` xen-pciback upstreaming [was Re: Xen patches merged to upstream Linux 2.6.36, plans for 2.6.37?] Josip Rodin
2011-05-26 12:44   ` Konrad Rzeszutek Wilk [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110526124413.GD3386@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=joy@entuzijast.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.