From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the mediatek tree
Date: Thu, 8 Jan 2026 06:46:35 +1100 [thread overview]
Message-ID: <20260108064635.42e96272@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
34e7595912cf ("arm64: dts: mediatek: Apply mt8395-radxa DT overlay at build time")
d977b61d3803 ("arm64: dts: mediatek: mt7988: add dtbs with applied overlays for bpi-r4 (pro)")
0516c548883b ("arm64: dts: mediatek: mt7986: add dtbs with applied overlays for bpi-r3")
These are commits
ce7b1d58609a ("arm64: dts: mediatek: Apply mt8395-radxa DT overlay at build time")
0773bc6ab7ec ("arm64: dts: mediatek: mt7988: add dtbs with applied overlays for bpi-r4 (pro)")
987697749def ("arm64: dts: mediatek: mt7986: add dtbs with applied overlays for bpi-r3")
In Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-01-07 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 19:46 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-01 1:13 linux-next: duplicate patches in the mediatek tree Stephen Rothwell
2024-04-28 21:32 Stephen Rothwell
2024-04-29 7:37 ` AngeloGioacchino Del Regno
2023-06-29 22:44 Stephen Rothwell
2023-09-10 23:00 ` 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=20260108064635.42e96272@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=angelogioacchino.delregno@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
/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