From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Chanho Min <chanho.min@lge.com>, Tom Lendacky <thomas.lendacky@amd.com>
Subject: [PATCH 0/2] Make DTs compliant with bindings
Date: Wed, 9 Mar 2022 23:54:01 +0530 [thread overview]
Message-ID: <20220309182403.12968-1-singh.kuldeep87k@gmail.com> (raw)
These patches are an attempt to fix DTs which are not in compliant with
pl022 binding.
LG1312, LG1313 and amd seattle platforms require fix in clock
properties.
https://lore.kernel.org/linux-spi/20220309171847.5345-1-singh.kuldeep87k@gmail.com/T/#u
Based on git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git,
master.
Rob, could you please help in picking these patches as git tree is not
specified in MAINTAINERS.
Kuldeep Singh (2):
arm64: dts: lg131x: Update spi clock properties
arm64: dts: seattle: Update spi node 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(-)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: Chanho Min <chanho.min@lge.com>, Tom Lendacky <thomas.lendacky@amd.com>
Subject: [PATCH 0/2] Make DTs compliant with bindings
Date: Wed, 9 Mar 2022 23:54:01 +0530 [thread overview]
Message-ID: <20220309182403.12968-1-singh.kuldeep87k@gmail.com> (raw)
These patches are an attempt to fix DTs which are not in compliant with
pl022 binding.
LG1312, LG1313 and amd seattle platforms require fix in clock
properties.
https://lore.kernel.org/linux-spi/20220309171847.5345-1-singh.kuldeep87k@gmail.com/T/#u
Based on git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git,
master.
Rob, could you please help in picking these patches as git tree is not
specified in MAINTAINERS.
Kuldeep Singh (2):
arm64: dts: lg131x: Update spi clock properties
arm64: dts: seattle: Update spi node 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(-)
--
2.25.1
next reply other threads:[~2022-03-09 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 18:24 Kuldeep Singh [this message]
2022-03-09 18:24 ` [PATCH 0/2] Make DTs compliant with bindings Kuldeep Singh
2022-03-09 18:24 ` [PATCH 1/2] arm64: dts: lg131x: Update spi clock properties Kuldeep Singh
2022-03-09 18:24 ` Kuldeep Singh
2022-03-09 18:24 ` [PATCH 2/2] arm64: dts: seattle: Update spi node properties Kuldeep Singh
2022-03-09 18:24 ` Kuldeep Singh
2022-03-10 23:18 ` [PATCH 0/2] Make DTs compliant with bindings Rob Herring
2022-03-10 23:18 ` Rob Herring
2022-03-11 2:59 ` Kuldeep Singh
2022-03-11 2:59 ` Kuldeep Singh
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=20220309182403.12968-1-singh.kuldeep87k@gmail.com \
--to=singh.kuldeep87k@gmail.com \
--cc=chanho.min@lge.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thomas.lendacky@amd.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 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.