From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL v2] ARM: DTS: Fix broken GICv2 register maps
Date: Mon, 30 Jan 2017 21:06:48 -0800 [thread overview]
Message-ID: <20170131050648.GB16560@localhost> (raw)
In-Reply-To: <1485766389-30811-1-git-send-email-marc.zyngier@arm.com>
Hi Marc,
On Mon, Jan 30, 2017 at 08:53:09AM +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.
>
> * From v1: Dropped the controvertial cortex-a15-gic->arm,gic-400
> change in the example, at Rob's request.
>
> The following changes since commit 49def1853334396f948dcb4cedb9347abb318df5:
>
> Linux 4.10-rc4 (2017-01-15 16:21:59 -0800)
Any reason you had to base this on -rc4? We usually stick to an older -rc
for all our branches, this cycle it's -rc3.
Care to respin? Or I can just pick over the patches, as long as you don't
need them as a stable base somewhere else.
-Olof
next prev parent reply other threads:[~2017-01-31 5:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 8:53 [PULL v2] ARM: DTS: Fix broken GICv2 register maps Marc Zyngier
2017-01-31 5:06 ` Olof Johansson [this message]
2017-01-31 9:41 ` Marc Zyngier
2017-02-07 14:07 ` Arnd Bergmann
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=20170131050648.GB16560@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