All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Rob Herring <robherring2@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Russell King <linux@armlinux.org.uk>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warnings in Linus' tree
Date: Sat, 04 Apr 2020 01:31:53 +0200	[thread overview]
Message-ID: <cc05ef520927c64614acc54bf27e3df080f1fbbe.camel@suse.de> (raw)
In-Reply-To: <CAL_JsqKd=3zw4uAbDthp-c=_+4XFup0XEdw8nHOmJDzxS2-qSA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3358 bytes --]

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@canb.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


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-04-03 23:32 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 22:19 linux-next: build warnings in Linus' tree Stephen Rothwell
2020-04-03 23:16 ` Rob Herring
2020-04-03 23:31   ` Nicolas Saenz Julienne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-14  6:57 Stephen Rothwell
2022-05-26  7:21 Stephen Rothwell
2022-01-27  4:30 Stephen Rothwell
2022-01-27  6:01 ` Christoph Hellwig
2022-01-27 16:44   ` Stephen Rothwell
2022-01-27  4:24 Stephen Rothwell
2021-11-22 22:44 Stephen Rothwell
2021-11-23  7:04 ` Borislav Petkov
2021-11-05  5:03 Stephen Rothwell
2021-10-12 10:56 Stephen Rothwell
2021-10-12 20:13 ` Randy Dunlap
2021-10-08  5:47 Stephen Rothwell
2021-10-08  5:47 ` Stephen Rothwell
2021-10-10 21:27 ` Stephen Rothwell
2021-10-10 21:27   ` Stephen Rothwell
2021-10-11 20:42   ` Rob Herring
2021-10-11 20:42     ` Rob Herring
2021-10-12 14:39     ` Arnd Bergmann
2021-10-12 14:39       ` Arnd Bergmann
2021-10-13 22:12       ` Anatolij Gustschin
2021-10-13 22:12         ` Anatolij Gustschin
2021-10-13 22:17         ` Rob Herring
2021-10-13 22:17           ` Rob Herring
2021-10-13 22:28           ` Anatolij Gustschin
2021-10-13 22:28             ` Anatolij Gustschin
2021-10-13 23:22             ` Rob Herring
2021-10-13 23:22               ` Rob Herring
2021-10-14  8:44         ` Arnd Bergmann
2021-10-14  8:44           ` Arnd Bergmann
2021-10-14 12:24           ` Anatolij Gustschin
2021-10-14 12:24             ` Anatolij Gustschin
2020-09-07 23:11 Stephen Rothwell
2020-09-08 13:14 ` Josh Poimboeuf
2020-09-09  0:15   ` Stephen Rothwell
2017-11-13 21:52 Stephen Rothwell
2017-11-13 22:03 ` Linus Torvalds
2013-07-04  4:58 Stephen Rothwell
2013-07-09 21:48 ` Nikolova, Tatyana E
2011-08-15  1:57 Stephen Rothwell
2011-05-23  1:25 Stephen Rothwell
2011-05-23  2:31 ` Eduardo Silva
2011-01-14  0:17 Stephen Rothwell
2011-01-14  0:09 Stephen Rothwell
2011-01-14  0:17 ` Andrew Morton
2011-01-14  1:06   ` Greg KH
2010-08-17  1:24 Stephen Rothwell
2010-08-30  1:42 ` Stephen Rothwell
2010-08-30  6:08   ` Zhang Rui
2010-09-03  2:01     ` Stephen Rothwell
2010-09-03  2:36     ` Len Brown
2010-09-17  4:26     ` Stephen Rothwell
2010-09-27 13:31       ` Stephen Rothwell
2010-08-07  2:21 Stephen Rothwell
2010-08-07  8:13 ` Vikas Chaudhary

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=cc05ef520927c64614acc54bf27e3df080f1fbbe.camel@suse.de \
    --to=nsaenzjulienne@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=robherring2@gmail.com \
    --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 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.