From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the mediatek tree
Date: Mon, 11 Sep 2023 09:00:46 +1000 [thread overview]
Message-ID: <20230911085725.6778bf3c@canb.auug.org.au> (raw)
In-Reply-To: <20230630084457.3a483c12@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
Hi all,
On Fri, 30 Jun 2023 08:44:57 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
>
> 1139eb7bf5ef ("arm64: dts: mediatek: mt8186: Wire up CPU frequency/voltage scaling")
> 113b5cc06f44 ("arm64: dts: mediatek: mt8173-elm: remove panel model number in DT")
> 2cb0317922e2 ("arm64: dts: mt7986: add pwm-fan and cooling-maps to BPI-R3 dts")
> 320f2af8c387 ("arm64: dts: mt7986: add thermal and efuse")
> 4a7fcb3cdf6c ("arm64: dts: mt7986: use size of reserved partition for bl2")
> 58d2424d9f83 ("arm64: dts: mediatek: mt8192: Add missing dma-ranges to soc node")
> 5e042912c86b ("arm64: dts: mediatek: mt8183: kukui: Add scp firmware-name")
> 7c8cf2a19228 ("arm64: dts: mediatek: mt8192: Fix CPUs capacity-dmips-mhz")
> 861af546db4f ("arm64: dts: mt7986: add thermal-zones")
> 8b018984aad7 ("arm64: dts: mt8173: Power on panel regulator on boot")
> c45c921fb524 ("arm64: dts: mt7986: increase bl2 partition on NAND of Bananapi R3")
> ccc2a6d8446c ("arm64: dts: mt8195: Add video decoder node")
> d0b4508ad0b5 ("arm64: dts: mediatek: Add cpufreq nodes for MT8192")
> e5b12f3b851f ("arm64: dts: mediatek: mt8186: Add CCI node and CCI OPP table")
> eb5aab271611 ("arm64: dts: mediatek: mt8186: Add GPU speed bin NVMEM cells")
> f38ff7d3b0f1 ("arm64: dts: mediatek: mt8186: Wire up GPU voltage/frequency scaling")
> fd6d9a1c9819 ("arm64: dts: mt8192: Add video-codec nodes")
Those duplicates still exist in the mediatek tree
(git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git#for-next).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-09-10 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 22:44 linux-next: duplicate patches in the mediatek tree Stephen Rothwell
2023-09-10 23:00 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-28 21:32 Stephen Rothwell
2024-04-29 7:37 ` AngeloGioacchino Del Regno
2024-07-01 1:13 Stephen Rothwell
2026-01-07 19:46 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=20230911085725.6778bf3c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--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