devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sm8650: Fix compile warnings in USB controller node
Date: Wed, 3 Dec 2025 16:07:38 +0100	[thread overview]
Message-ID: <3b29618b-71bb-46f1-bd55-e7291effc8d1@kernel.org> (raw)
In-Reply-To: <20251203144856.2711440-3-krishna.kurapati@oss.qualcomm.com>

On 03/12/2025 15:48, Krishna Kurapati wrote:
> With W=1, the following error comes up:
> 
> Warning (avoid_unnecessary_addr_size): /soc@0/usb@a600000: unnecessary #address-cells/#size-cells without "ranges", "dma-ranges" or child "reg" or "ranges" property
> 
> This is because the child node being removed during flattening and moving
> to latest bindings.
> 
> Fixes: 77e1f16b9302 ("arm64: dts: qcom: sm8650: Flatten the USB nodes")
> Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
> ---


Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Best regards,
Krzysztof

  reply	other threads:[~2025-12-03 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 14:48 [PATCH 0/2] Fix compile warnings for SM8550 and SM8650 Krishna Kurapati
2025-12-03 14:48 ` [PATCH 1/2] arm64: dts: qcom: sm8550: Fix compile warnings in USB controller node Krishna Kurapati
2025-12-03 15:07   ` Krzysztof Kozlowski
2025-12-08  8:26     ` Neil Armstrong
2025-12-03 14:48 ` [PATCH 2/2] arm64: dts: qcom: sm8650: " Krishna Kurapati
2025-12-03 15:07   ` Krzysztof Kozlowski [this message]
2025-12-06  4:01 ` [PATCH 0/2] Fix compile warnings for SM8550 and SM8650 Dmitry Baryshkov
2025-12-06  4:06 ` 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=3b29618b-71bb-46f1-bd55-e7291effc8d1@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krishna.kurapati@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).