From: "Rafał Miłecki" <rafal@milecki.pl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Arnd Bergmann <arnd@arndb.de>, Joel Stanley <joel@jms.id.au>,
Florian Fainelli <f.fainelli@gmail.com>,
Olof Johansson <olof@lixom.net>,
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: Thu, 06 Oct 2022 07:14:05 +0200 [thread overview]
Message-ID: <d019295b10f2d84e945d8e55ecc52e4f@milecki.pl> (raw)
In-Reply-To: <20221006111725.01ed0eac@canb.auug.org.au>
On 2022-10-06 02:17, Stephen Rothwell wrote:
> On Wed, 05 Oct 2022 09:21:21 +0200 "Arnd Bergmann" <arnd@arndb.de>
> wrote:
>>
>> 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.
>
> I applied the revert to the merge of the arm-soc tree today and *all*
> the warnings are gone.
As explained by Joel, there are dtc and yaml warnings.
Not "*all*" warnings are gone
dtc warnings are gone
yaml warnings are back
Which may be OK, just clarifying.
next prev parent reply other threads:[~2022-10-06 5:20 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
2022-10-06 0:17 ` Stephen Rothwell
2022-10-06 5:14 ` Rafał Miłecki [this message]
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=d019295b10f2d84e945d8e55ecc52e4f@milecki.pl \
--to=rafal@milecki.pl \
--cc=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=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).