From: p.fedin@samsung.com (Pavel Fedin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 TRIVIAL 0/2] ARM: Enable GICv2m on 32-bit virt machine
Date: Fri, 04 Sep 2015 16:29:50 +0300 [thread overview]
Message-ID: <cover.1441373056.git.p.fedin@samsung.com> (raw)
qemu implementation of "virt" includes GICv2m. This series allows to use
it also on ARM32 architecture.
v3 => v4:
- Split into two patches as requested by Marc Zyngier
- Use specialized word extraction macros instead of #ifdef
v1 => v2:
Added verbose explanation in commit message
v2 => v3:
Fixed build warning in irq-gic-v2m.c
v1 => v2:
Added verbose explanation in commit message
Pavel Fedin (2):
ARM: Enable GICv2m on 32-bit virt machine
ARM: Fix GICv2m build warning on 32 bits
arch/arm/Kconfig | 1 +
arch/arm/include/asm/Kbuild | 1 +
drivers/irqchip/irq-gic-v2m.c | 4 ++--
3 files changed, 4 insertions(+), 2 deletions(-)
--
2.4.4
next reply other threads:[~2015-09-04 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 13:29 Pavel Fedin [this message]
2015-09-04 13:29 ` [PATCH v4 TRIVIAL 1/2] ARM: Enable GICv2m on 32-bit virt machine Pavel Fedin
2015-09-04 13:29 ` [PATCH v4 TRIVIAL 2/2] ARM: Fix GICv2m build warning on 32 bits Pavel Fedin
2015-09-04 17:14 ` Marc Zyngier
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=cover.1441373056.git.p.fedin@samsung.com \
--to=p.fedin@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.