linux-kernel - Re: linux-next: build warnings in Linus' 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] [day] [month] [year] [list]

Date:   Sat, 04 Apr 2020 01:31:53 +0200
From:   Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To:     Rob Herring <robherring2@...il.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Russell King <linux@...linux.org.uk>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build warnings in Linus' tree

Hi Rob, Stephen,

On Fri, 2020-04-03 at 17:16 -0600, Rob Herring wrote:
> +Nicolas
> 
> On Fri, Apr 3, 2020 at 4:19 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> > Hi all,
> > 
> > Today's linux-next build of Linus' tree (arm multi_v7_defconfig) produced
> > these warnings:
> > 
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > arch/arm/boot/dts/bcm2835-rpi.dtsi:18.4-15: Warning (dma_ranges_format):
> > /soc/firmware:dma-ranges: empty "dma-ranges" property but its #address-
cells 
> > (2) differs from /soc (1)
> > 
> > I have no idea what caused this :-(
> 
> A dtc update combined with changes that landed in the above file after
> I tested and fixed the new warnings.

Sorry for the warnings. A fix is already making its way into the soc fixes
tree.

Here's the commit for reference: https://lkml.org/lkml/2020/3/26/445

Regards,
Nicolas


Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)