From: Florian Fainelli <f.fainelli@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Re: linux-next: unexpected files in the broadcom tree
Date: Tue, 9 Sep 2025 15:44:20 -0700 [thread overview]
Message-ID: <4ba5dff8-9f07-4750-8f42-42f885646964@gmail.com> (raw)
In-Reply-To: <20250910083713.4c5ef7d2@canb.auug.org.au>
On 9/9/25 15:37, Stephen Rothwell wrote:
> 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")
>
Now fixed, thanks Stephen!
--
Florian
prev parent reply other threads:[~2025-09-09 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 22:37 Stephen Rothwell
2025-09-09 22:44 ` Florian Fainelli [this message]
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=4ba5dff8-9f07-4750-8f42-42f885646964@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrea.porta@suse.com \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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
all inboxes | Powered by JetHome®