From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL] ARM: DTS: Fix broken GICv2 register maps
Date: Sun, 29 Jan 2017 17:19:31 -0800 [thread overview]
Message-ID: <20170130011931.GA3133@localhost> (raw)
In-Reply-To: <1485342160-23286-1-git-send-email-marc.zyngier@arm.com>
On Wed, Jan 25, 2017 at 11:02:40AM +0000, Marc Zyngier wrote:
> ARM-soc folks,
>
> Please find below the pull request for a DT fix affecting a large
> number of 32bit platforms, which has been acked by a number of
> platform maintainers.
>
> The following changes since commit 49def1853334396f948dcb4cedb9347abb318df5:
>
> Linux 4.10-rc4 (2017-01-15 16:21:59 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/gic-v2-dt
>
> for you to fetch changes up to ed2799b62a323ea041e0475ac8bff8e023e224f1:
>
> ARM: DTS: Fix register map for virt-capable GIC (2017-01-23 15:44:58 +0000)
Hi,
Replied to the patch a little earlier today, holding off on this until that is
sorted.
prev parent reply other threads:[~2017-01-30 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 11:02 [PULL] ARM: DTS: Fix broken GICv2 register maps Marc Zyngier
2017-01-30 1:19 ` Olof Johansson [this message]
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=20170130011931.GA3133@localhost \
--to=olof@lixom.net \
--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).