From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alexandre Torgue <alexandre.torgue@st•com>
Cc: Olof Johansson <olof@lixom•net>, Arnd Bergmann <arnd@arndb•de>,
ARM <linux-arm-kernel@lists•infradead.org>,
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: Wed, 18 Sep 2024 06:43:49 +1000 [thread overview]
Message-ID: <20240918064349.79dc0a1e@canb.auug.org.au> (raw)
In-Reply-To: <20240906120821.6ca2ac3d@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
Hi all,
On Fri, 6 Sep 2024 12:08:21 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> The following commits are also in the arm-soc tree as different commits
> (but the same patches):
>
> 078dc4752822 ("ARM: dts: stm32: stm32mp151a-prtt1l: Fix QSPI configuration")
> 76e16f3549e8 ("ARM: dts: stm32: Keep MDIO bus in AF across suspend DH STM32MP13xx DHCOR DHSBC board")
> 835dfbca3781 ("ARM: dts: stm32: Add ethernet MAC nvmem cells to DH STM32MP13xx DHCOR DHSBC board")
> 8388a6e67f22 ("dt-bindings: arm: stm32: Add compatible strings for Protonic boards")
> a15ad86d4b65 ("ARM: dts: stm32: Add MECIO1 and MECT1S board variants")
> b14c9f6bd0ba ("ARM: dts: stm32: Use SAI to generate bit and frame clock on STM32MP15xx DHCOM PDK2")
> b512ce39b570 ("ARM: dts: stm32: Sort properties in audio endpoints on STM32MP15xx DHCOM PDK2")
> c00176c49e94 ("ARM: dts: stm32: Describe PHY LEDs in DH STM32MP13xx DHCOR DHSBC board DT")
> ce923f5d2804 ("ARM: dts: stm32: Switch bitclock/frame-master to flag on STM32MP15xx DHCOM PDK2")
> d3557e468f68 ("ARM: dts: stm32: Disable PHY clock output on DH STM32MP13xx DHCOR DHSBC board")
> efab072ce426 ("ARM: dts: stm32: Add missing gpio options for sdmmc2_d47_pins_d")
Those patches are now in Linus' tree (as different commits). Please
clean up the stm32 tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-09-17 20:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 2:08 linux-next: duplicate patches in the stm32 tree Stephen Rothwell
2024-09-17 20:43 ` 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-07-16 21:53 Stephen Rothwell
2024-07-31 23:46 ` 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=20240918064349.79dc0a1e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=alexandre.torgue@st$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=olof@lixom$(echo .)net \
/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