All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Roger Quadros <rogerq@kernel.org>
Cc: "Raghavendra, Vignesh" <vigneshr@ti.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Tero Kristo <kristo@kernel.org>,
	Santosh Shilimkar <ssantosh@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
	<devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the ti tree
Date: Thu, 5 Oct 2023 08:29:21 -0500	[thread overview]
Message-ID: <20231005132921.2vg6kdcr273bh7et@cabbage> (raw)
In-Reply-To: <2905cfc2-912f-4620-9455-2e91586a2839@kernel.org>

On 16:12-20231005, Roger Quadros wrote:
> Hi,
> 
> On 05/10/2023 11:25, Raghavendra, Vignesh wrote:
> > + Rob and DT list
> > 
> > Hi Stephen
> > 
> > On 10/5/2023 8:45 AM, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> [I may have missed this yesterday, sorry]
> >>
> >> After merging the ti tree, today's linux-next build (arm64 defconfig)
> >> produced these warnings:
> >>
> >> arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso:65.8-140.3: Warning (avoid_default_addr_size): /fragment@3/__overlay__: Relying on default #address-cells value
> >> arch/arm64/boot/dts/ti/k3-am642-evm-nand.dtso:65.8-140.3: Warning (avoid_default_addr_size): /fragment@3/__overlay__: Relying on default #size-cells value
> >>
> >> Introduced by commit
> >>
> >>   45a0c06571e1 ("arm64: dts: ti: am642-evm: Add overlay for NAND expansion card")
> >>
> > 
> > Thanks for the report. I will drop the offending comment.
> > 
> > Roger,
> > 
> > Sorry, this would need to be fixed in dtc or need exception from DT
> > maintainers to ignore the warnings.
> 
> Please don't drop this patch as the issue is not with the patch but with
> the dtc tool itself.
> 
> As this is a DT overlay there is no way to specify address-cells/size-cells
> of parent here. This will be resolved only after merge with base tree.
> 
> This will be fixed in next dtc sync.
> https://www.spinics.net/lists/devicetree-compiler/msg04036.html
> 
> See further discussion here
> https://lore.kernel.org/all/CAL_JsqLmv904+_2EOmsQ__y1yLDvsT+_02i85phuh0cpe7X8NQ@mail.gmail.com/
> 

Roger, build warnings are a strict NO,NO for kernel. Lets bring in the
series *after* the dtc sync is complete.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

  reply	other threads:[~2023-10-05 15:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05  3:15 linux-next: build warnings after merge of the ti tree Stephen Rothwell
2023-10-05  8:25 ` Raghavendra, Vignesh
2023-10-05  8:25   ` Raghavendra, Vignesh
2023-10-05 13:12   ` Roger Quadros
2023-10-05 13:29     ` Nishanth Menon [this message]
2023-10-06 12:03       ` Roger Quadros
2023-10-06 13:55         ` Rob Herring
2023-10-06 15:41           ` Roger Quadros

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=20231005132921.2vg6kdcr273bh7et@cabbage \
    --to=nm@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=ssantosh@kernel.org \
    --cc=vigneshr@ti.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.