From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jeremy Fitzhardinge <Jeremy.Fitzhardinge@citrix.com>,
Chris Wright <chrisw@sous-sol.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xen PV on HVM and initial domain merge in linux-next
Date: Wed, 20 Oct 2010 16:16:17 +0100 [thread overview]
Message-ID: <alpine.DEB.2.00.1010201455160.10348@kaball-desktop> (raw)
In-Reply-To: <20101020113256.3647b1d9.sfr@canb.auug.org.au>
On Wed, 20 Oct 2010, Stephen Rothwell wrote:
> Hi Stefano,
>
> [just casting the net a bit wider ...]
>
> On Tue, 19 Oct 2010 18:51:47 +0100 Stefano Stabellini <stefano.stabellini@eu.citrix.com> wrote:
> >
> > I forgot to CC the LKML and linux-next...
> >
> > On Tue, 19 Oct 2010, Stefano Stabellini wrote:
> > > Stephen,
> > > I have two patch series to merge in linux-next:
> > >
> > > PV on HVM: receive interrupts as xen events
> > > xen: initial domain support
> > >
> > > they have all the acked-by needed and are both stable since several
> > > weeks, however they depend on Konrad's xen-pcifront series and for this
> > > reason I waited until now to ask for a merge in linux-next.
> > >
> > > Could you please pull:
> > >
> > > git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git linux-next-initial-domain-v4
> > >
> > > it contains both series rebased on Konrad's pcifront series merged on
> > > linux-next (warning: it still contains the merge commit of
> > > xen-pcifront-0.8.2 in linux-next).
> > > Let me know if you have any conflicts or if you need me to change the
> > > branch somehow.
>
> Not following the Xen develpment at all, I would like to have a positive
> reply from the listed Xen contacts, please,
>
Sure.
Jeremy?
> I do have concerns that this is turning up so late, but I realise that
> that is mainly due to a misunderstanding on the part of some of the Xen
> community.
>
Thank you very much for understanding!
> Also, the above tree is based on next-20101019 which means that I cannot
> use it as is. All the trees merged into linux-next must be base on some
> other stable tree (almost always Linus' tree). linux-next is rebuilt
> from scratch every day, so I cannot ever include a previous day's version.
>
> Merging in other stable trees is OK (as long as the other maintainer is
> aware of that and makes sure that their tree does not reabse).
>
> Basically what you send to me should be what you intend to send to Linus
> during the next merge window.
All right.
I merged Jeremy's and Konrad's branches (the ones you just merged on
linux-next) on top of linux 2.6.36 rc8, then I rebased my series on top
of the result.
Please checkout this branch:
git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git 2.6.36-rc8-initial-domain-v5
and let me know if it is suitable, it shouldn't have any merge
conflicts.
Cheers,
Stefano
next prev parent reply other threads:[~2010-10-20 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1010191254460.2423@kaball-desktop>
2010-10-19 17:51 ` Stefano Stabellini
2010-10-20 0:32 ` Stephen Rothwell
2010-10-20 15:11 ` [Xen-devel] " Dan Magenheimer
2010-10-20 16:43 ` Chris Wright
2010-10-20 15:16 ` Stefano Stabellini [this message]
2010-10-20 15:28 ` Konrad Rzeszutek Wilk
2010-10-20 15:47 ` Stefano Stabellini
2010-10-20 23:45 ` Stephen Rothwell
2010-10-21 13:44 ` Stefano Stabellini
2010-10-20 15:45 ` Jeremy Fitzhardinge
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=alpine.DEB.2.00.1010201455160.10348@kaball-desktop \
--to=stefano.stabellini@eu.citrix.com \
--cc=Jeremy.Fitzhardinge@citrix.com \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=virtualization@lists.osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®