linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "Joel Stanley" <joel@jms.id.au>,
	"Florian Fainelli" <f.fainelli@gmail.com>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Olof Johansson" <olof@lixom.net>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	linux-next <linux-next@vger.kernel.org>,
	ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: linux-next: build warnings after merge of the broadcom tree
Date: Wed, 05 Oct 2022 09:21:21 +0200	[thread overview]
Message-ID: <f8416a63-3460-4b43-8532-2d5eacea4457@app.fastmail.com> (raw)
In-Reply-To: <CACPK8Xecn8ZREAqcLcuZHjA=NhaanRMKu4W39okAkBFX4aaOnw@mail.gmail.com>

On Wed, Oct 5, 2022, at 8:02 AM, Joel Stanley wrote:
> On Wed, 5 Oct 2022 at 03:01, Florian Fainelli <f.fainelli@gmail.com> wrote:
>> >> I am still seeing these warnings.
>> >>
>> >> The above commit is now
>> >>
>> >>    61dc1e3850a6 ("ARM: dts: BCM5301X: Add basic PCI controller properties")
>> >
>> > Has any progress been made with this?  This commit is now in the
>> > arm-soc tree.
>>
>> Yes, I was hoping to get some feedback on this patch:
>>
>> https://lore.kernel.org/all/20220920210213.3268525-1-f.fainelli@gmail.com/
>>
>> but I suppose being the ARM SoC maintainer I can just go ahead and push it.

Sorry, I unfortunately missed this patch, and forgot about the
original issue.

> I'd send a revert of the change. Rafal can then re-submit a series
> that fixes the dtc warnings as well as the yaml warning once they have
> been tested and reviewed.
>
> The yaml warnings aren't seen by other developers, as they require the
> tools to be installed, but those from dtc are.

Agreed. Alternatively, we could just remove the pcie@ nodes from
bcm5301x as a hotfix, as they are clearly not usable in the
current form, and none of the three versions (5.19, Rafał's
patch missing ranges, and Florian's patch with incorrect ranges)
actually conform to the binding.

I'll tentatively apply the revert for now so I can send the pull
request tonight. If someone comes up with a better fix, I can
use that instead.

     Arnd

  reply	other threads:[~2022-10-05  7:21 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
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 [this message]
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=f8416a63-3460-4b43-8532-2d5eacea4457@app.fastmail.com \
    --to=arnd@arndb.de \
    --cc=f.fainelli@gmail.com \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=rafal@milecki.pl \
    --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).