From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] ARM: berlin: DT changes for v4.4 (round 1)
Date: Thu, 15 Oct 2015 14:42:12 +0200 [thread overview]
Message-ID: <561F9F24.1050801@gmail.com> (raw)
In-Reply-To: <6053924.4novCdxIMG@wuerfel>
On 14.10.2015 17:44, Arnd Bergmann wrote:
> On Friday 09 October 2015 20:48:13 Sebastian Hesselbarth wrote:
>> this is round 1 of Marvell Berlin DT changes for v4.4. There is
>> some improvement in serial aliases/stdout path, cpufreq properties,
>> and PWM nodes for all SoCs. The cpufreq properties depend on cpuclk
>> being available, therefore this branch has a dependency with the
>> cpuclk topic PR sent earlier.
>>
>
> Pulled into next/dt, thanks!
Hi Arnd,
the prerequisite cpuclk topic branch didn't make it into arm-soc causing
a build failure on bg2q dts files.
Unfortunately, cpuclk topic branch touches both, dt-includes and driver
code. I was hoping you could also pull the topic branch with berlin/dt.
I am open for suggestions how to deal with it now and in the future.
Sebastian
next prev parent reply other threads:[~2015-10-15 12:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 18:48 [GIT PULL 1/3] ARM: berlin: CPU clock topic for v4.4 (round 1) Sebastian Hesselbarth
2015-10-09 18:48 ` [GIT PULL 2/3] ARM: berlin: DT changes " Sebastian Hesselbarth
2015-10-14 15:44 ` Arnd Bergmann
2015-10-15 12:42 ` Sebastian Hesselbarth [this message]
2015-10-15 13:23 ` Arnd Bergmann
2015-10-15 18:44 ` [GIT PULL] ARM: berlin: DT CPU clock fixup for v4.4 Sebastian Hesselbarth
2015-10-15 18:53 ` Arnd Bergmann
2015-10-15 18:55 ` Sebastian Hesselbarth
2015-10-15 19:04 ` [GIT PULL] ARM: berlin: CPU clock driver for v4.4 (round 1) Sebastian Hesselbarth
2015-10-15 20:43 ` Arnd Bergmann
2015-10-15 20:43 ` Arnd Bergmann
2015-10-09 18:48 ` [GIT PULL 3/3] ARM: berlin: SoC changes " Sebastian Hesselbarth
2015-10-15 20: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=561F9F24.1050801@gmail.com \
--to=sebastian.hesselbarth@gmail.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 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.