linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Zhen Lei <thunder.leizhen@huawei.com>,
	Rob Herring <robh+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: broadcom: remove an unused property dma-ranges
Date: Tue, 13 Oct 2020 20:12:37 -0700	[thread overview]
Message-ID: <fa40441b-6ae1-6018-3da6-424d0252c1ba@gmail.com> (raw)
In-Reply-To: <20201013060623.1711-2-thunder.leizhen@huawei.com>



On 10/12/2020 11:06 PM, Zhen Lei wrote:
> stingray-usb.dtsi is finally included by three dts files:
> bcm958802a802x.dts, bcm958742k.dts and bcm958742t.dts. I searched all
> these three entire expanded dts files, and each of them contains only one
> dma-ranges. No conversion range is specified, so it cannot work properly.
> I think this property "dma-ranges" is added by mistake, just remove it.
> Otherwise, the following error will be reported when any YAML detection
> is performed on arm64.
> 
> arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning \
> (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but \
> its #address-cells (1) differs from / (2)
> arch/arm64/boot/dts/broadcom/stingray/stingray-usb.dtsi:7.3-14: Warning \
> (dma_ranges_format): /usb:dma-ranges: empty "dma-ranges" property but \
> its #size-cells (1) differs from / (2)
> 
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>

This looks fine to me, Scott, Ray do you want to Ack this patch before I 
take it?
-- 
Florian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-10-14  3:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13  6:06 [PATCH 0/2] eliminate two common errors reported by any yaml on arm64 Zhen Lei
2020-10-13  6:06 ` [PATCH 1/2] arm64: dts: broadcom: remove an unused property dma-ranges Zhen Lei
2020-10-14  3:12   ` Florian Fainelli [this message]
2020-10-14  7:38     ` Arnd Bergmann
2020-10-14 13:36       ` Leizhen (ThunderTown)
2020-10-14 13:43         ` Leizhen (ThunderTown)
2020-10-14 14:02         ` Arnd Bergmann
2020-10-16  7:06           ` Leizhen (ThunderTown)
2020-10-16  7:53             ` Leizhen (ThunderTown)
2020-10-13  6:06 ` [PATCH 2/2] arm64: dts: qcom: " Zhen Lei

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=fa40441b-6ae1-6018-3da6-424d0252c1ba@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=agross@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=thunder.leizhen@huawei.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;
as well as URLs for NNTP newsgroup(s).