From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
soc@kernel.org
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: [GIT PULL (RESEND)] ARM: dts: uniphier: UniPhier DT updates for v5.6
Date: Fri, 24 Jan 2020 12:36:10 +0900 [thread overview]
Message-ID: <CAK7LNARYrzv4QU-eXxqYCcC9dziJmx9F02YNZ3mMnF47EfL3fA@mail.gmail.com> (raw)
Hi Olof, Arnd,
Here are UniPhier DT (32bit) updates for the v5.6 merge window.
(I am resending this with soc@kernel.org in the To: list)
Please pull!
The following changes since commit e42617b825f8073569da76dc4510bfa019b1c35a:
Linux 5.5-rc1 (2019-12-08 14:57:55 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-uniphier.git
tags/uniphier-dt-v5.6
for you to fetch changes up to 37f3e0096f716b06338a4771633b32b8e2a36f7f:
ARM: dts: uniphier: add reset-names to NAND controller node
(2020-01-18 00:56:09 +0900)
----------------------------------------------------------------
UniPhier ARM SoC DT updates for v5.6
- Add pinmux nodes for I2C ch5, ch6
- Add reset-names to NAND controller node
----------------------------------------------------------------
Masahiro Yamada (2):
ARM: dts: uniphier: add pinmux nodes for I2C ch5, ch6
ARM: dts: uniphier: add reset-names to NAND controller node
arch/arm/boot/dts/uniphier-ld4.dtsi | 3 ++-
arch/arm/boot/dts/uniphier-pinctrl.dtsi | 10 ++++++++++
arch/arm/boot/dts/uniphier-pro4.dtsi | 3 ++-
arch/arm/boot/dts/uniphier-pro5.dtsi | 3 ++-
arch/arm/boot/dts/uniphier-pxs2.dtsi | 3 ++-
arch/arm/boot/dts/uniphier-sld8.dtsi | 3 ++-
6 files changed, 20 insertions(+), 5 deletions(-)
--
Best Regards
Masahiro Yamada
reply other threads:[~2020-01-24 3:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAK7LNARYrzv4QU-eXxqYCcC9dziJmx9F02YNZ3mMnF47EfL3fA@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.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).