From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Florian Fainelli <f.fainelli@gmail•com>
Cc: Andrea della Porta <andrea.porta@suse•com>,
Florian Fainelli <florian.fainelli@broadcom•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: unexpected files in the broadcom tree
Date: Wed, 10 Sep 2025 08:37:13 +1000 [thread overview]
Message-ID: <20250910083713.4c5ef7d2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
Hi all,
While fetching the broadcom tree, I noticed that the following unexpected
files were present:
arch/arm64/boot/dts/broadcom/bcm2712-rpi-5-b.dts.orig
arch/arm64/boot/dts/broadcom/rp1-common.dtsi.orig
They are introduced in commit
b00f5cbb7abb ("arm64: dts: broadcom: Enable USB devicetree entries for Rpi5")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-09-09 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 22:37 Stephen Rothwell [this message]
2025-09-09 22:44 ` linux-next: unexpected files in the broadcom tree Florian Fainelli
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=20250910083713.4c5ef7d2@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andrea.porta@suse$(echo .)com \
--cc=f.fainelli@gmail$(echo .)com \
--cc=florian.fainelli@broadcom$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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