linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC DT PM Domain Updates for v4.7
Date: Thu, 28 Apr 2016 18:27:25 +0200	[thread overview]
Message-ID: <CAMuHMdWnt4ceLuu-eddbMQDSFvHHVgoyUNM2V=SYO9R0XrJDMQ@mail.gmail.com> (raw)
In-Reply-To: <5702417.rnCUR69ruo@wuerfel>

Hi Arnd,

On Thu, Apr 28, 2016 at 5:56 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Wednesday 27 April 2016 14:20:34 Simon Horman wrote:
>> Please consider these Renesas ARM based SoC DT pm-domain updates for v4.7.
>>
>> This pull requests is based on a merge of:
>>
>> * "[GIT PULL] Second Round of Renesas ARM Based SoC R-Car SYSC Updates for
>>   v4.7", tagged as renesas-rcar-sysc2-for-v4.7, which you have already
>>   pulled.
>> * "[GIT PULL v2] Renesas ARM Based SoC DT Updates for v4.7",
>>   tagged as renesas-dt-for-v4.7, which you have also already pulled.
>>
>> The reason for the somewhat tedious base on
>> renesas-rcar-sysc2-for-v4.7, which provides driver changes,
>> is a hard run-time dependency.
>>
>> I also have a similar set of changes for arm64 which I will send separately.
>
> Ok, I've started a next/late branch for this now, but unless something
> else comes up that needs to be sent much later, I expect to submit
> this as the last pull request at the same time as all the other ones
> for 4.7.

Thanks!

> For further clarification, am I right reading the above as meaning that
> a 4.7 kernel is expected to still work with the dts files from 4.6,
> but not the other way round?

That's correct.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2016-04-28 16:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27  4:20 [GIT PULL] Renesas ARM Based SoC DT PM Domain Updates for v4.7 Simon Horman
2016-04-27  4:20 ` [PATCH 01/10] ARM: dts: r8a7779: Add SYSC PM Domains Simon Horman
2016-04-27  4:20 ` [PATCH 02/10] ARM: dts: r8a7790: " Simon Horman
2016-04-27  4:20 ` [PATCH 03/10] ARM: dts: r8a7791: " Simon Horman
2016-04-27  4:20 ` [PATCH 04/10] ARM: dts: r8a7793: " Simon Horman
2016-04-27  4:20 ` [PATCH 05/10] ARM: dts: r8a7794: " Simon Horman
2016-04-27  4:20 ` [PATCH 06/10] ARM: dts: r8a7779: Use SYSC "always-on" PM Domain Simon Horman
2016-04-27  4:20 ` [PATCH 07/10] ARM: dts: r8a7790: " Simon Horman
2016-04-27  4:20 ` [PATCH 08/10] ARM: dts: r8a7791: " Simon Horman
2016-04-27  4:20 ` [PATCH 09/10] ARM: dts: r8a7793: " Simon Horman
2016-04-27  4:20 ` [PATCH 10/10] ARM: dts: r8a7794: " Simon Horman
2016-04-28 15:56 ` [GIT PULL] Renesas ARM Based SoC DT PM Domain Updates for v4.7 Arnd Bergmann
2016-04-28 16:27   ` Geert Uytterhoeven [this message]
2016-04-28 23:22     ` Simon Horman

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='CAMuHMdWnt4ceLuu-eddbMQDSFvHHVgoyUNM2V=SYO9R0XrJDMQ@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --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).