From: Olof Johansson <olof@lixom.net>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Ludovic Desroches <ludovic.desroches@microchip.com>,
arm@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: at91: DT for 4.21
Date: Wed, 12 Dec 2018 13:05:53 -0800 [thread overview]
Message-ID: <20181212210553.jk4uznjimi37fd7p@localhost> (raw)
In-Reply-To: <20181211171112.GA30925@piout.net>
On Tue, Dec 11, 2018 at 06:11:12PM +0100, Alexandre Belloni wrote:
> Arnd, Olof,
>
> Here is the DT pull request for 4.21. The clock DT binding switch has
> been in -next for a while and doesn't seem to have any issue.
>
> This is based on the 4.20 fixes branch that you alredy pulled.
>
> The following changes since commit 4ab7ca092c3c7ac8b16aa28eba723a8868f82f14:
>
> ARM: dts: at91: sama5d2: use the divided clock for SMC (2018-11-21 11:50:32 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/at91/linux tags/at91-4.21-dt
>
> for you to fetch changes up to d8007306f6ad18f2ba0dcad68ffe9b2fd1d56bfb:
>
> ARM: dts: at91: nattis: initialize the BLON pin as output-low early (2018-11-21 12:24:50 +0100)
>
> ----------------------------------------------------------------
> AT91 DT for 4.21
>
> - Switch most platforms to the new clock binding
> - Small improvement for Axentia nattis
Merged, but how does this affect downstream users who have out-of-tree DTS
files that include the SoC dtsi? Seems like lots of stuff would break.
-Olof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-12 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 17:11 [GIT PULL] ARM: at91: DT for 4.21 Alexandre Belloni
2018-12-12 21:05 ` Olof Johansson [this message]
2018-12-12 22:27 ` Alexandre Belloni
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=20181212210553.jk4uznjimi37fd7p@localhost \
--to=olof@lixom.net \
--cc=alexandre.belloni@bootlin.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
/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