From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Shriram Rajagopalan <rshriram@gmail.com>
Cc: Stefano@acsinet11.oracle.com,
Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Re: 2.6.39 merge window (git pulls and what is planned to go in)
Date: Fri, 11 Mar 2011 09:21:09 -0500 [thread overview]
Message-ID: <20110311142109.GA4880@dumpdata.com> (raw)
In-Reply-To: <1299834691.17339.1797.camel@zakaz.uk.xensource.com>
On Fri, Mar 11, 2011 at 09:11:31AM +0000, Ian Campbell wrote:
> On Thu, 2011-03-10 at 19:29 +0000, Konrad Rzeszutek Wilk wrote:
> > Probably over the weekend Linus is going to open the merge window.
> >
> > This merge window is much more complicated than the previous
> > one b/c we got a lot of good stuff.
> >
> > For my sanity and book-keeping I was thinking to email Linus
> > five git pull requests:
> [...]
> > .. and then during the next week of the two weeks merge window:
> [...]
> > In this order or so.
>
> Seems sane. I'm going to rebase my dev tree onto all these now (I think
> I've got most of it already)
OK. #linux-next is you place then.
>
> > In other trees by other maintainers we have:
> [...]
> > git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git has
> > xen suspend cleanups
> > PVonHVM improvements - makes spinlocks be PV aware, balloon in HVM
>
> Are Shriram's suspend/checkpoint patches in the pipeline somewhere?
<head smack> I knew I forgot something.
The last I heard he was battling PVonHVM shutdown issues during his
testing of his patches.
Shririam?
>
> > The things that are not going in 2.6.39 are:
> >
> > devel/xen-pciback-0.4.driver [xen-pciback]
>
> Targeting 2.6.40?
Yes.
>
> > devel/xen-blkback-v1 [xen-blkback]
>
> 2.6.40 again?
Yeah, I think by that time any issues/failures would show up and I
can fix them.
>
> > git://xenbits.xen.org/people/ianc/linux-2.6 upstream/dom0/backend/netback
> > [xen-netback - well, it could if the network maintainers are comfortable
> > with the driver, but I think it is still going through the review]
>
> I've got another round of (minor) review feedback to address, I'm still
> a little bit hopeful for a 2.6.39 merge.
>
> Either way this will go through the net tree not us.
<nods>
>
> Ian.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-03-11 14:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 19:29 2.6.39 merge window (git pulls and what is planned to go in) Konrad Rzeszutek Wilk
2011-03-11 1:26 ` Jeremy Fitzhardinge
2011-03-11 9:11 ` Ian Campbell
2011-03-11 14:21 ` Konrad Rzeszutek Wilk [this message]
2011-03-15 15:12 ` Ian Campbell
2011-03-15 16:53 ` Shriram Rajagopalan
2011-03-15 19:52 ` Ian Campbell
2011-03-15 20:12 ` Shriram Rajagopalan
2011-03-15 20:58 ` Ian Campbell
2011-03-15 22:16 ` Konrad Rzeszutek Wilk
2011-03-16 9:40 ` Ian Campbell
2011-03-16 14:29 ` Konrad Rzeszutek Wilk
2011-03-16 14:38 ` Ian Campbell
2011-03-16 15:28 ` Shriram Rajagopalan
2011-03-16 15:58 ` Konrad Rzeszutek Wilk
2011-03-16 16:08 ` Ian Campbell
2011-03-16 16:21 ` Konrad Rzeszutek Wilk
2011-03-16 16:24 ` Ian Campbell
2011-03-16 17:12 ` Shriram Rajagopalan
2011-03-18 13:59 ` Re: 2.6.39 merge window - git pulls and what went in Konrad Rzeszutek Wilk
2011-03-18 14:36 ` Stephan Seitz
2011-03-18 14:39 ` Stefano Stabellini
2011-03-16 15:23 ` Re: 2.6.39 merge window (git pulls and what is planned to go in) Shriram Rajagopalan
2011-03-16 16:15 ` Ian Campbell
2011-03-11 11:00 ` Stefano Stabellini
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=20110311142109.GA4880@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Stefano@acsinet11.oracle.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=jeremy@goop.org \
--cc=rshriram@gmail.com \
--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.