From: ian.campbell@citrix.com (Ian Campbell)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] [PATCH v2 0/3] arm/arm64: Detect Xen support earlier
Date: Wed, 25 Feb 2015 16:40:40 +0000 [thread overview]
Message-ID: <1424882440.18290.22.camel@citrix.com> (raw)
In-Reply-To: <20150225163417.GN12377@arm.com>
On Wed, 2015-02-25 at 16:34 +0000, Will Deacon wrote:
> On Wed, Feb 25, 2015 at 04:22:33PM +0000, Julien Grall wrote:
> > Hello,
> >
> > Ping? Any comments from ARM's maintainers on theses patches (at least #2)?
>
> I couldn't care less :)
>
> The arm64 part is boring in the good sense of the word.
May Julien take that as an Acked-by? ;-)
Given this is all about Xen really I suppose it makes most sense to take
it via the Xen tree.
Russell, does that work for you? (arch/arm bits are in patch #2 if you
want to take a look)
Ian.
next prev parent reply other threads:[~2015-02-25 16:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 13:51 [PATCH v2 0/3] arm/arm64: Detect Xen support earlier Julien Grall
2015-02-18 13:51 ` [PATCH v2 1/3] arm/xen: Correctly check if the event channel interrupt is present Julien Grall
2015-02-26 18:08 ` Stefano Stabellini
2015-02-18 13:51 ` [PATCH v2 2/3] arm,arm64/xen: move Xen initialization earlier Julien Grall
2015-04-07 17:26 ` Stefano Stabellini
2015-05-06 14:04 ` Stefano Stabellini
2015-02-18 13:51 ` [PATCH v2 3/3] xen/arm: allow console=hvc0 to be omitted for guests Julien Grall
2015-02-18 15:25 ` Ian Campbell
2015-02-18 15:50 ` Rob Herring
2015-02-18 16:03 ` Ian Campbell
2015-02-26 18:22 ` Stefano Stabellini
2015-02-27 9:34 ` Ian Campbell
2015-02-27 9:47 ` Stefano Stabellini
2015-02-25 16:22 ` [PATCH v2 0/3] arm/arm64: Detect Xen support earlier Julien Grall
2015-02-25 16:34 ` Will Deacon
2015-02-25 16:38 ` Julien Grall
2015-02-25 16:40 ` Ian Campbell [this message]
2015-02-25 18:01 ` [Xen-devel] " Will Deacon
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=1424882440.18290.22.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).