From: Julien Grall <julien.grall@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Julien Grall <julien.grall@citrix.com>,
stefano.stabellini@citrix.com, ian.campbell@citrix.com
Subject: [PATCH 0/8] xen/arm: gic-v2: Detect automatically aliased GIC400
Date: Tue, 22 Sep 2015 18:47:34 +0100 [thread overview]
Message-ID: <1442944062-4324-1-git-send-email-julien.grall@citrix.com> (raw)
Hi all,
Only patch #7 is related to subject. The others are clean up of code I looked
while I was working on this series.
Regards,
Julien Grall (8):
xen/arm: gic: Make clear the GIC node is passed to make_hwdom_dt_node
xen/arm: Retrieve the correct number of cells when building dom0 DT
xen/arm: Fix comment coding style in handle_node in domain_build.c
xen/arm: Warn when a device tree path will be re-used by Xen
xen/arm: vgic-v2: Drop cbase from arch_domain
xen/arm: gic: Check the size of the CPU and vCPU interface retrieved
from DT
xen/arm: gic-v2: Detect automatically aliased GIC400
xen/arm: platform: Drop the quirks callback
xen/arch/arm/domain_build.c | 30 ++++++++---
xen/arch/arm/gic-hip04.c | 18 +++----
xen/arch/arm/gic-v2.c | 98 +++++++++++++++++++++++++++---------
xen/arch/arm/gic-v3.c | 34 +++++++++----
xen/arch/arm/gic.c | 6 ++-
xen/arch/arm/platform.c | 10 ----
xen/arch/arm/platforms/xgene-storm.c | 6 ---
xen/arch/arm/vgic-v2.c | 51 ++++++++++++-------
xen/common/device_tree.c | 38 +++++++++++---
xen/include/asm-arm/domain.h | 1 -
xen/include/asm-arm/gic.h | 6 ++-
xen/include/asm-arm/platform.h | 14 ------
xen/include/asm-arm/vgic.h | 3 +-
xen/include/xen/device_tree.h | 23 ++++++++-
14 files changed, 225 insertions(+), 113 deletions(-)
--
2.1.4
next reply other threads:[~2015-09-22 17:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 17:47 Julien Grall [this message]
2015-09-22 17:47 ` [PATCH 1/8] xen/arm: gic: Make clear the GIC node is passed to make_hwdom_dt_node Julien Grall
2015-09-25 15:48 ` Ian Campbell
2015-09-28 14:49 ` Julien Grall
2015-09-22 17:47 ` [PATCH 2/8] xen/arm: Retrieve the correct number of cells when building dom0 DT Julien Grall
2015-09-25 16:01 ` Ian Campbell
2015-09-28 14:59 ` Julien Grall
2015-09-28 15:19 ` Ian Campbell
2015-09-28 15:25 ` Julien Grall
2015-09-22 17:47 ` [PATCH 3/8] xen/arm: Fix comment coding style in handle_node in domain_build.c Julien Grall
2015-09-25 16:03 ` Ian Campbell
2015-09-25 16:48 ` Ian Campbell
2015-09-22 17:47 ` [PATCH 4/8] xen/arm: Warn when a device tree path will be re-used by Xen Julien Grall
2015-09-25 16:10 ` Ian Campbell
2015-09-28 15:44 ` Julien Grall
2015-09-28 15:55 ` Ian Campbell
2015-09-28 16:05 ` Julien Grall
2015-09-28 17:46 ` Julien Grall
2015-09-22 17:47 ` [PATCH 5/8] xen/arm: vgic-v2: Drop cbase from arch_domain Julien Grall
2015-09-25 16:11 ` Ian Campbell
2015-09-22 17:47 ` [PATCH 6/8] xen/arm: gic: Check the size of the CPU and vCPU interface retrieved from DT Julien Grall
2015-09-25 16:19 ` Ian Campbell
2015-09-28 16:29 ` Julien Grall
2015-09-22 17:47 ` [PATCH 7/8] xen/arm: gic-v2: Detect automatically aliased GIC400 Julien Grall
2015-09-25 16:26 ` Ian Campbell
2015-09-28 18:07 ` Julien Grall
2015-09-29 10:51 ` Ian Campbell
2015-09-22 17:47 ` [PATCH 8/8] xen/arm: platform: Drop the quirks callback Julien Grall
2015-09-25 16:27 ` Ian Campbell
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=1442944062-4324-1-git-send-email-julien.grall@citrix.com \
--to=julien.grall@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@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).