From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-next@vger.kernel.org
Subject: Re: xen PV on HVM and initial domain merge in linux-next
Date: Tue, 19 Oct 2010 18:51:47 +0100 [thread overview]
Message-ID: <alpine.DEB.2.00.1010191847290.10348@kaball-desktop> (raw)
In-Reply-To: <alpine.DEB.2.00.1010191254460.2423@kaball-desktop>
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.
>
> Many thanks in advance,
>
> Stefano Stabellini
>
next parent reply other threads:[~2010-10-19 17:52 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 [this message]
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
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.1010191847290.10348@kaball-desktop \
--to=stefano.stabellini@eu.citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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®