From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>, xen-devel@lists.xenproject.org
Cc: Andre Przywara <andre.przywara@arm.com>,
stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH 2/2] xen/arm: gic-v3: Allow Xen to run on hardware reporting GICv4
Date: Tue, 15 Sep 2015 12:15:28 +0100 [thread overview]
Message-ID: <1442315728.3549.375.camel@citrix.com> (raw)
In-Reply-To: <55F7FADC.8090605@citrix.com>
On Tue, 2015-09-15 at 12:02 +0100, Julien Grall wrote:
> What about:
>
> "The GICv4 is an extension of GICv3 (see 1.1 in ARM IHI 0069A) which
> means that the GICv3 driver can run normally on a GICv4 hardware.
>
> Though, the GICv4-only feature won't be used."
I've a few grammatical quibbles, plus I think s/reporting/supporting/ in
the title.
So how about:
Subject: xen/arm: gic-v3: Allow Xen to run on hardware supporting GICv4
GICv4 is an extension of GICv3 (see 1.1 in ARM IHI 0069A) which means that
the GICv3 driver can run normally on GICv4 hardware.
The GICv4-only features currently won't be used.
S-o-b: etc
next prev parent reply other threads:[~2015-09-15 11:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 15:32 [PATCH 0/2] GICv3: Clean up + enable support on GICv4 Julien Grall
2015-09-14 15:32 ` [PATCH 1/2] xen/arm: gic-v3: Clean-up the GIC*_PIDR2_* definitions Julien Grall
2015-09-15 9:35 ` Ian Campbell
2015-09-14 15:32 ` [PATCH 2/2] xen/arm: gic-v3: Allow Xen to run on hardware reporting GICv4 Julien Grall
2015-09-15 9:49 ` Ian Campbell
2015-09-15 10:28 ` Andre Przywara
2015-09-15 11:02 ` Julien Grall
2015-09-15 11:15 ` Ian Campbell [this message]
2015-09-15 11:19 ` Julien Grall
2015-09-24 11:32 ` Ian Campbell
2015-09-21 15:54 ` [PATCH 0/2] GICv3: Clean up + enable support on GICv4 Julien Grall
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=1442315728.3549.375.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andre.przywara@arm.com \
--cc=julien.grall@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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).