From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: PING: [PATCH v4 TRIVIAL 1/2] ARM: Enable GICv2m on 32-bit virt machine
Date: Wed, 7 Oct 2015 11:23:13 +0100 [thread overview]
Message-ID: <20151007102313.GG21513@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <017801d100dc$77fe3a90$67faafb0$@samsung.com>
On Wed, Oct 07, 2015 at 11:45:06AM +0300, Pavel Fedin wrote:
> Hello! I have retested this on 4.3rc3, everything is fine. 2/2 has
> been already picked up, so this is the only bit left.
Sorry, I've no idea if this is the right thing to do.
I know we have MSI-using platforms working on 32-bit ARM at the moment,
which brings up the question about msi.h in your patch, and what are
the implications for the existing MSI using platforms of having
PCI_MSI_IRQ_DOMAIN enabled in a multiplatform kernel.
I don't know enough to be able to merge this patch, and there's not
enough information in the commit message either. Plus, with the lack
of acks from people in ARM, I'm very reluctant to take this (I don't
know whether the original patch got any, it's fallen out of my mailbox.)
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-10-07 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 8:45 PING: [PATCH v4 TRIVIAL 1/2] ARM: Enable GICv2m on 32-bit virt machine Pavel Fedin
2015-10-07 10:23 ` Russell King - ARM Linux [this message]
2015-10-07 11:02 ` Pavel Fedin
2015-10-07 11:29 ` Russell King - ARM Linux
2015-10-07 12:43 ` Marc Zyngier
2015-10-07 16:26 ` Russell King - ARM Linux
2015-10-07 12:14 ` Pavel Fedin
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=20151007102313.GG21513@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).