From: Lars Povlsen <lars.povlsen@microchip.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: SoC Team <soc@kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>,
Microchip UNG Driver List <UNGLinuxDriver@microchip.com>,
<devicetree@vger.kernel.org>
Subject: [GIT PULL] Devicetree patches for Sparx5 v5.11
Date: Thu, 10 Dec 2020 13:12:31 +0100 [thread overview]
Message-ID: <87ft4dq2q8.fsf@microchip.com> (raw)
Hi Arnd!
Alex made me aware we're late with DT updates for 5.11, I hope you can
fit these 2 patches in. Sorry!
---Lars
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
https://github.com/microchip-ung/linux-upstream.git sparx5-next
for you to fetch changes up to 7e1f91cbfa0d330fad61c621389373cff81898fd:
arm64: dts: sparx5: Add SGPIO devices (2020-12-10 11:55:31 +0100)
----------------------------------------------------------------
Lars Povlsen (2):
arm64: dts: sparx5: Add reset support
arm64: dts: sparx5: Add SGPIO devices
arch/arm64/boot/dts/microchip/sparx5.dtsi | 96 ++++++++
arch/arm64/boot/dts/microchip/sparx5_pcb125.dts | 5 +
.../boot/dts/microchip/sparx5_pcb134_board.dtsi | 258 +++++++++++++++++++++
.../boot/dts/microchip/sparx5_pcb135_board.dtsi | 55 +++++
4 files changed, 414 insertions(+)
--
Lars Povlsen,
Microchip
WARNING: multiple messages have this Message-ID (diff)
From: Lars Povlsen <lars.povlsen@microchip.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: devicetree@vger.kernel.org, SoC Team <soc@kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>,
Microchip UNG Driver List <UNGLinuxDriver@microchip.com>
Subject: [GIT PULL] Devicetree patches for Sparx5 v5.11
Date: Thu, 10 Dec 2020 13:12:31 +0100 [thread overview]
Message-ID: <87ft4dq2q8.fsf@microchip.com> (raw)
Message-ID: <20201210121231.UmgJVTolfn0Pd59xD5pFrqZgC1jYgmo9sya7vozdMgs@z> (raw)
Hi Arnd!
Alex made me aware we're late with DT updates for 5.11, I hope you can
fit these 2 patches in. Sorry!
---Lars
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
https://github.com/microchip-ung/linux-upstream.git sparx5-next
for you to fetch changes up to 7e1f91cbfa0d330fad61c621389373cff81898fd:
arm64: dts: sparx5: Add SGPIO devices (2020-12-10 11:55:31 +0100)
----------------------------------------------------------------
Lars Povlsen (2):
arm64: dts: sparx5: Add reset support
arm64: dts: sparx5: Add SGPIO devices
arch/arm64/boot/dts/microchip/sparx5.dtsi | 96 ++++++++
arch/arm64/boot/dts/microchip/sparx5_pcb125.dts | 5 +
.../boot/dts/microchip/sparx5_pcb134_board.dtsi | 258 +++++++++++++++++++++
.../boot/dts/microchip/sparx5_pcb135_board.dtsi | 55 +++++
4 files changed, 414 insertions(+)
--
Lars Povlsen,
Microchip
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-12-10 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 12:12 Lars Povlsen [this message]
2020-12-10 12:12 ` [GIT PULL] Devicetree patches for Sparx5 v5.11 Lars Povlsen
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=87ft4dq2q8.fsf@microchip.com \
--to=lars.povlsen@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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 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.