From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: <xen-devel@lists.xensource.com>, <linux-kernel@vger.kernel.org>,
"David Vrabel" <david.vrabel@citrix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
<boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v2 0/3] hvc_xen: fix xenboot on x86 and export to ARM
Date: Fri, 26 Feb 2016 14:28:38 +0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1602261426410.4219@kaball.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1602251206500.17248@kaball.uk.xensource.com>
On Thu, 25 Feb 2016, Stefano Stabellini wrote:
> Hi all,
>
> this series exports xenboot on ARM and ARM64 as earlycon, and gets
> xenboot fully working again for PV DomUs on x86 (currently the xenboot
> output only goes to the hypervisor via hypercall and not to the DomU
> console).
>
> Cheers,
>
> Stefano
>
>
> Stefano Stabellini (3):
> hvc_xen: add earlycon support
> hvc_xen: fix xenboot for DomUs
> hvc_xen: make early_printk work with HVM guests
Boris has reviewed all the patches in the series. Are you all happy if I
go ahead and commit the whole series to xentip/for-linus-4.6 ?
next prev parent reply other threads:[~2016-02-26 14:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 12:09 [PATCH v2 0/3] hvc_xen: fix xenboot on x86 and export to ARM Stefano Stabellini
2016-02-25 12:10 ` [PATCH v2 1/3] hvc_xen: add earlycon support Stefano Stabellini
2016-02-25 15:00 ` Boris Ostrovsky
2016-02-25 12:10 ` [PATCH v2 2/3] hvc_xen: fix xenboot for DomUs Stefano Stabellini
2016-02-25 15:04 ` Boris Ostrovsky
2016-02-26 15:39 ` Stefano Stabellini
2016-02-26 16:09 ` Boris Ostrovsky
2016-02-26 16:57 ` Stefano Stabellini
2016-02-25 12:10 ` [PATCH v2 3/3] hvc_xen: make early_printk work with HVM guests Stefano Stabellini
2016-02-25 15:13 ` Boris Ostrovsky
2016-02-26 14:28 ` Stefano Stabellini [this message]
2016-02-26 14:41 ` [PATCH v2 0/3] hvc_xen: fix xenboot on x86 and export to ARM David Vrabel
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.02.1602261426410.4219@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).