From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Vinod Koul <vkoul@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Gross <agross@kernel.org>,
devicetree@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH v3 0/3] arm64: dts: qcom: Get rid of some warnings
Date: Sat, 2 Jul 2022 22:56:54 -0500 [thread overview]
Message-ID: <165682055970.445910.6231160279000811511.b4-ty@linaro.org> (raw)
In-Reply-To: <20220606065035.553533-1-vkoul@kernel.org>
On Mon, 6 Jun 2022 12:20:32 +0530, Vinod Koul wrote:
> 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.
>
> [...]
Applied, thanks!
[1/3] arm64: dts: qcom: sm8450: rename interconnect nodes
commit: 12cfafe7b78876133474f4b3e44e0464a94f61b0
[2/3] arm64: dts: qcom: sm8350: Move qup-opp-tables out of soc node
commit: e2eedde448a9be6202fd9965aef29d4b6607ee67
[3/3] arm64: dts: qcom: sm8250: Move qup-opp-table out of soc node
commit: 191c85b852c122e9282797ae3ce2a36083f1e9a9
Best regards,
--
Bjorn Andersson <bjorn.andersson@linaro.org>
prev parent reply other threads:[~2022-07-03 4:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 6:50 [PATCH v3 0/3] arm64: dts: qcom: Get rid of some warnings Vinod Koul
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 ` Bjorn Andersson [this message]
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=165682055970.445910.6231160279000811511.b4-ty@linaro.org \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.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 \
--cc=vkoul@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.