From: Vinod Koul <vkoul@kernel.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Andy Gross <agross@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] arm64: dts: qcom: Get rid of some warnings
Date: Mon, 6 Jun 2022 12:20:32 +0530 [thread overview]
Message-ID: <20220606065035.553533-1-vkoul@kernel.org> (raw)
This attempts to make W=1 free from warnings for all SM* dts files.
Bunch of these are releated to node not having valid unit address and being
present under soc node. So moving it out fixed that. Interconnect node was
simple rename to remove unit address which was not really valid for these
nodes.
Changes in v3:
- rebase on v5.19-rc1
Changes in v2:
- drop the sound and dsi node changes
*** SUBJECT HERE ***
*** BLURB HERE ***
Vinod Koul (3):
arm64: dts: qcom: sm8450: rename interconnect nodes
arm64: dts: qcom: sm8350: Move qup-opp-tables out of soc node
arm64: dts: qcom: sm8250: Move qup-opp-table out of soc node
arch/arm64/boot/dts/qcom/sm8250.dtsi | 38 +++++++-------
arch/arm64/boot/dts/qcom/sm8350.dtsi | 76 ++++++++++++++--------------
arch/arm64/boot/dts/qcom/sm8450.dtsi | 4 +-
3 files changed, 59 insertions(+), 59 deletions(-)
--
2.34.1
next reply other threads:[~2022-06-06 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 6:50 Vinod Koul [this message]
2022-06-06 6:50 ` [PATCH v3 1/3] arm64: dts: qcom: sm8450: rename interconnect nodes Vinod Koul
2022-06-06 6:50 ` [PATCH v3 2/3] arm64: dts: qcom: sm8350: Move qup-opp-tables out of soc node Vinod Koul
2022-06-06 6:50 ` [PATCH v3 3/3] arm64: dts: qcom: sm8250: Move qup-opp-table " Vinod Koul
2022-07-03 3:56 ` [PATCH v3 0/3] arm64: dts: qcom: Get rid of some warnings Bjorn Andersson
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=20220606065035.553533-1-vkoul@kernel.org \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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.