From: "Rob Herring (Arm)" <robh@kernel.org>
To: soc@kernel.org, Kuldeep Singh <singh.kuldeep87k@gmail.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chanho Min <chanho.min@lge.com>,
Vladimir Zapolskiy <vz@mleia.com>,
Piotr Wojtaszczyk <piotr.wojtaszczyk@timesys.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v2 0/2] arm64: dts: PL022 clock fixes
Date: Tue, 05 Nov 2024 15:18:38 -0600 [thread overview]
Message-ID: <20241105-dts-spi-fixes-v2-0-623501e5d1ca@kernel.org> (raw)
Arnd, this series[1] from 2.5 years ago was never applied. There was
some discussion on the lpc32xx patch, but nothing on the first 2
patches. So I'm resending the first 2. Please apply directly.
Rob
[1] https://lore.kernel.org/all/20220311093800.18778-1-singh.kuldeep87k@gmail.com/
Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
---
Kuldeep Singh (2):
arm64: dts: seattle: Update spi clock properties
arm64: dts: lg131x: Update spi clock properties
arch/arm64/boot/dts/amd/amd-seattle-soc.dtsi | 8 ++++----
arch/arm64/boot/dts/lg/lg1312.dtsi | 8 ++++----
arch/arm64/boot/dts/lg/lg1313.dtsi | 8 ++++----
3 files changed, 12 insertions(+), 12 deletions(-)
---
base-commit: 6f2ca0f00f319c694ad5bb494b64745a43b40756
change-id: 20241105-dts-spi-fixes-9c24e7763f3b
Best regards,
--
Rob Herring (Arm) <robh@kernel.org>
next reply other threads:[~2024-11-05 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 21:18 Rob Herring (Arm) [this message]
2024-11-05 21:18 ` [PATCH RESEND v2 1/2] arm64: dts: seattle: Update spi clock properties Rob Herring (Arm)
2024-11-05 21:18 ` [PATCH RESEND v2 2/2] arm64: dts: lg131x: " Rob Herring (Arm)
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=20241105-dts-spi-fixes-v2-0-623501e5d1ca@kernel.org \
--to=robh@kernel.org \
--cc=chanho.min@lge.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piotr.wojtaszczyk@timesys.com \
--cc=singh.kuldeep87k@gmail.com \
--cc=soc@kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=thomas.lendacky@amd.com \
--cc=vz@mleia.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
all inboxes | Powered by JetHome®