From: arnd@arndb.de (Arnd Bergmann)
To: linus-amlogic@lists.infradead.org
Subject: [GIT PULL] Amlogic 64-bit DT changes for v4.9
Date: Wed, 14 Sep 2016 17:41:37 +0200 [thread overview]
Message-ID: <9855488.GIzjicgLjX@wuerfel> (raw)
In-Reply-To: <7h7fat25g4.fsf@baylibre.com>
On Friday, September 2, 2016 5:27:23 PM CEST Kevin Hilman wrote:
> The pull request below is for the DT changes for 64-bit Amlogic
> platforms.
>
> The DT additions for the new clock/reset support are dependent on DT
> bindings/includes that were merged via the clock tree, so this branch
> includes a merge of an immtable branch (clk/clk-gxbb-meson-ao) from the
> clock tree to handle those dependencies.
>
> Due to the dependency, it's fine with me if this goes into next/late
> instead of next/dt64.
>
Pulled into next/late, thanks!
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Amlogic 64-bit DT changes for v4.9
Date: Wed, 14 Sep 2016 17:41:37 +0200 [thread overview]
Message-ID: <9855488.GIzjicgLjX@wuerfel> (raw)
In-Reply-To: <7h7fat25g4.fsf@baylibre.com>
On Friday, September 2, 2016 5:27:23 PM CEST Kevin Hilman wrote:
> The pull request below is for the DT changes for 64-bit Amlogic
> platforms.
>
> The DT additions for the new clock/reset support are dependent on DT
> bindings/includes that were merged via the clock tree, so this branch
> includes a merge of an immtable branch (clk/clk-gxbb-meson-ao) from the
> clock tree to handle those dependencies.
>
> Due to the dependency, it's fine with me if this goes into next/late
> instead of next/dt64.
>
Pulled into next/late, thanks!
Arnd
next prev parent reply other threads:[~2016-09-14 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 0:27 [GIT PULL] Amlogic 64-bit DT changes for v4.9 Kevin Hilman
2016-09-03 0:27 ` Kevin Hilman
2016-09-14 15:41 ` Arnd Bergmann [this message]
2016-09-14 15:41 ` 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=9855488.GIzjicgLjX@wuerfel \
--to=arnd@arndb.de \
--cc=linus-amlogic@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.