From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alexandre Torgue <alexandre.torgue@st•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 stm32 tree
Date: Thu, 1 Aug 2024 09:46:49 +1000 [thread overview]
Message-ID: <20240801094649.0ea1f73d@canb.auug.org.au> (raw)
In-Reply-To: <20240717075355.10020fec@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
Hi all,
On Wed, 17 Jul 2024 07:53:55 +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):
>
> 1245911be805 ("ARM: multi_v7_defconfig: Add MCP23S08 pinctrl support")
> 1eafc48af859 ("arm64: stm32: enable scmi regulator for stm32")
> 2599b1f071f4 ("ARM: dts: stm32: Document output pins for PWMs on stm32mp135f-dk")
> 32bc9d195039 ("ARM: dts: stm32: Add ethernet support for DH STM32MP13xx DHCOR DHSBC board")
> 3389697affa5 ("arm64: dts: st: add HPDMA nodes on stm32mp251")
> 55dc557485c7 ("arm64: dts: st: add ethernet1 and ethernet2 support on stm32mp25")
> 5d6c1cef82a0 ("arm64: dts: st: describe power supplies for stm32mp257f-ev1 board")
> 9bcaeb10520a ("ARM: dts: stm32: add ethernet1 for STM32MP135F-DK board")
> a11b40677a34 ("regulator: Add STM32MP25 regulator bindings")
> a29ad03d8393 ("arm64: dts: st: add scmi regulators on stm32mp25")
> a43179fe3f09 ("arm64: dts: st: add eth2 pinctrl entries in stm32mp25-pinctrl.dtsi")
> a4a0254811cc ("ARM: dts: stm32: omit unused pinctrl groups from stm32mp13 dtb files")
> a80ce2d743fb ("ARM: dts: stm32: add ethernet1 and ethernet2 support on stm32mp13")
> ba3e48a76df3 ("ARM: dts: stm32: OP-TEE async notif interrupt for ST STM32MP15x boards")
> c62c13b4efe4 ("ARM: dts: stm32: add ethernet1/2 RMII pins for STM32MP13F-DK board")
> d41b45f29bc3 ("ARM: dts: stm32: order stm32mp13-pinctrl nodes")
> de2997982cf9 ("arm64: dts: st: enable Ethernet2 on stm32mp257f-ev1 board")
These duplicates are till there.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-07-31 23:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 21:53 linux-next: duplicate patches in the stm32 tree Stephen Rothwell
2024-07-31 23:46 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-22 1:38 Stephen Rothwell
2025-06-10 23:04 ` Stephen Rothwell
2025-05-01 1:37 Stephen Rothwell
2025-05-05 21:44 ` Stephen Rothwell
2025-01-05 22:37 Stephen Rothwell
2024-09-06 2:08 Stephen Rothwell
2024-09-17 20:43 ` Stephen Rothwell
2024-07-09 0:13 Stephen Rothwell
2024-04-30 1:04 Stephen Rothwell
2024-05-13 22:33 ` Stephen Rothwell
2024-05-14 23:54 ` Stephen Rothwell
2023-01-04 21:37 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=20240801094649.0ea1f73d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alexandre.torgue@st$(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