From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Allwinner arm64 DT changes for 4.10, bis
Date: Wed, 30 Nov 2016 16:54:49 +0100 [thread overview]
Message-ID: <5466789.d5zjXGQ0JJ@wuerfel> (raw)
In-Reply-To: <20161122144731.c6q6jxgd7cyeieqr@lukather>
On Tuesday, November 22, 2016 3:47:31 PM CET Maxime Ripard wrote:
> Hi Arnd, Olof,
>
> Here is a second run at the arm64 PR I sent earlier.
>
> We had a (build) dependency against the clock patches that have been
> merged by Stephen and Mike through the clock tree.
>
> Hence, this new PR is based on top of the tag I sent their way, and it
> supersedes the previous arm64 PR.
>
> I used this occasion to rename the patches prefix as Olof suggested in
> the earlier pull request.
Just to document what we discussed on IRC: I've dropped this pull
request, as we had already merged the previous one, and some other
patches on top. Instead, I changed the data in the sun50i-a64.dtsi
to reference the clocks and resets by numerical value rather than
by name, which fixes the build.
Arnd
prev parent reply other threads:[~2016-11-30 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 14:47 [GIT PULL] Allwinner arm64 DT changes for 4.10, bis Maxime Ripard
2016-11-30 15:54 ` Arnd Bergmann [this message]
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=5466789.d5zjXGQ0JJ@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