From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Joel Stanley" <joel@jms.id.au>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"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: Thu, 6 Oct 2022 11:17:25 +1100 [thread overview]
Message-ID: <20221006111725.01ed0eac@canb.auug.org.au> (raw)
In-Reply-To: <f8416a63-3460-4b43-8532-2d5eacea4457@app.fastmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 678 bytes --]
Hi Arnd,
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.
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-10-06 0:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220725095913.31e859ec@canb.auug.org.au>
[not found] ` <df8f4765-a804-cb50-bbb5-475925ba2036@milecki.pl>
2022-08-15 0:54 ` linux-next: build warnings after merge of the broadcom tree 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 [this message]
2022-10-06 5:14 ` Rafał Miłecki
2022-10-06 23:30 ` Stephen Rothwell
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=20221006111725.01ed0eac@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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=rafal@milecki.pl \
/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).