linux-kernel - Re: linux-next: build warnings after merge of the broadcom tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <df8f4765-a804-cb50-bbb5-475925ba2036@milecki.pl>
Date:   Mon, 25 Jul 2022 12:33:48 +0200
From:   Rafał Miłecki <rafal@...ecki.pl>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Florian Fainelli <f.fainelli@...il.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the broadcom tree

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@...00000/pcie@...00: missing ranges for PCI bridge (or not a bridge)
> arch/arm/boot/dts/bcm5301x.dtsi:248.21-254.5: Warning (pci_bridge): /axi@...00000/pcie@...00: missing ranges for PCI bridge (or not a bridge)
> arch/arm/boot/dts/bcm5301x.dtsi:256.21-262.5: Warning (pci_bridge): /axi@...00000/pcie@...00: 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@...00: '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@...00: '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@...00: '#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@...00: '#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@...00: '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.