linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL v2] ARM: DTS: Fix broken GICv2 register maps
Date: Tue, 31 Jan 2017 09:41:32 +0000	[thread overview]
Message-ID: <86zii77eib.fsf@arm.com> (raw)
In-Reply-To: <20170131050648.GB16560@localhost> (Olof Johansson's message of "Mon, 30 Jan 2017 21:06:48 -0800")

On Tue, Jan 31 2017 at 05:06:48 AM, Olof Johansson <olof@lixom.net> wrote:
> 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.

Ah, damn... No reason, just what I had at hand at the time this was put
together.

> 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.

If that works for you, please cherry pick the patches. I don't need them
to be based on anything in particular.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny.

  reply	other threads:[~2017-01-31  9:41 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
2017-01-31  9:41   ` Marc Zyngier [this message]
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=86zii77eib.fsf@arm.com \
    --to=marc.zyngier@arm.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 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).