linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <rafal@milecki.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Florian Fainelli <f.fainelli@gmail.com>
Cc: 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 broadcom tree
Date: Mon, 25 Jul 2022 12:33:48 +0200	[thread overview]
Message-ID: <df8f4765-a804-cb50-bbb5-475925ba2036@milecki.pl> (raw)
In-Reply-To: <20220725095913.31e859ec@canb.auug.org.au>

Hi,

On 25.07.2022 01:59, Stephen Rothwell wrote:
> After merging the broadcom tree, today's linux-next build (arm
> multi_v7_defconfig) produced these warnings:
> 
> arch/arm/boot/dts/bcm5301x.dtsi:240.21-246.5: Warning (pci_bridge): /axi@18000000/pcie@12000: missing ranges for PCI bridge (or not a bridge)
> arch/arm/boot/dts/bcm5301x.dtsi:248.21-254.5: Warning (pci_bridge): /axi@18000000/pcie@13000: missing ranges for PCI bridge (or not a bridge)
> arch/arm/boot/dts/bcm5301x.dtsi:256.21-262.5: Warning (pci_bridge): /axi@18000000/pcie@14000: missing ranges for PCI bridge (or not a bridge)

This is expected. My commit ef126d3f58d25 ("ARM: dts: BCM5301X: Add
basic PCI controller properties") reduced following warnings:

arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dtb: pcie@12000: 'device_type' is a required property
         From schema: /lib/python3.9/site-packages/dtschema/schemas/pci/pci-bus.yaml
arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dtb: pcie@12000: 'ranges' is a required property
         From schema: /lib/python3.9/site-packages/dtschema/schemas/pci/pci-bus.yaml
arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dtb: pcie@12000: '#address-cells' is a required property
         From schema: /lib/python3.9/site-packages/dtschema/schemas/pci/pci-bus.yaml
arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dtb: pcie@12000: '#size-cells' is a required property
         From schema: /lib/python3.9/site-packages/dtschema/schemas/pci/pci-bus.yaml


down to this one:

arch/arm/boot/dts/bcm47081-buffalo-wzr-600dhp2.dtb: pcie@12000: 'ranges' is a required property
         From schema: /lib/python3.9/site-packages/dtschema/schemas/pci/pci-bus.yaml


and basically does the right thing (adds required properties).


I'm fully aware "ranges" need to be added (it's mentioned in the commit)
and it's one of next things on my BCM5301X list.

So while my commits triggers that problem it also reduces warnings so
I'd say it's acceptable.

  reply	other threads:[~2022-07-25 10:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24 23:59 linux-next: build warnings after merge of the broadcom tree Stephen Rothwell
2022-07-25 10:33 ` Rafał Miłecki [this message]
2022-08-15  0:54   ` Stephen Rothwell
2022-08-30 23:16     ` Stephen Rothwell
2022-10-05  0:48       ` Stephen Rothwell
2022-10-05  2:29         ` Florian Fainelli
2022-10-05  6:02           ` Joel Stanley
2022-10-05  7:21             ` Arnd Bergmann
2022-10-06  0:17               ` Stephen Rothwell
2022-10-06  5:14                 ` Rafał Miłecki
2022-10-06 23:30                   ` Stephen Rothwell
2022-10-05  5:43       ` Rafał Miłecki

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=df8f4765-a804-cb50-bbb5-475925ba2036@milecki.pl \
    --to=rafal@milecki.pl \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).