From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Ux500 devicetree changes for v4.11
Date: Wed, 01 Feb 2017 10:49:00 +0100 [thread overview]
Message-ID: <1507979.mEcWZWFyc4@wuerfel> (raw)
In-Reply-To: <CACRpkdbOrFAgOn_vr8vLc9pGHqzkm+Os9MrhxJjs0xxzMHO+Og@mail.gmail.com>
On Wednesday, February 1, 2017 10:29:30 AM CET Linus Walleij wrote:
> Hi ARM SoC people,
>
> sorry for the late pull request, but these really should be going to
> 4.11. As late or whatever is fine.
>
> I found a number of bugs in the platform that had been accumulating
> and it would be nice to iron out most of them in v4.11.
>
> Please pull this to the ARM SoC tree in some apropriate branch.
>
> Yours,
> Linus Walleij
>
> The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77:
>
> Linux 4.10-rc1 (2016-12-25 16:13:08 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-stericsson.git
> tags/ux500-dt-1
>
> for you to fetch changes up to 3015d3b05239e33b42b1ae9ac408cc60fa4772ce:
>
> ARM: dts: add the AB8500 sysclk to the device trees (2017-01-31
> 22:15:06 +0100)
>
> ----------------------------------------------------------------
> Ux500 Device Tree updates for v4.11:
>
> This cleans the device tree a bit and rectifies some
> clocking bugs. They are in a sense regressions, but there
> is no hurry for this platform.
This is what the kbuild bot found for the patch submission:
>> arch/arm/boot/dts/ste-dbx5x0.dtsi:17:42: fatal error: dt-bindings/clock/ste-ab8500.h: No such file or directory
Can you have a look what caused it?
Arnd
next prev parent reply other threads:[~2017-02-01 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 9:29 [GIT PULL] Ux500 devicetree changes for v4.11 Linus Walleij
2017-02-01 9:49 ` Arnd Bergmann [this message]
2017-02-01 12:57 ` Linus Walleij
2017-02-07 14:35 ` 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=1507979.mEcWZWFyc4@wuerfel \
--to=arnd@arndb.de \
--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).