From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alexandre Torgue <alexandre.torgue@st•com>,
Arnd Bergmann <arnd@arndb•de>
Cc: 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: linux-next: duplicate patches in the stm32 tree
Date: Thu, 22 May 2025 11:38:16 +1000 [thread overview]
Message-ID: <20250522113816.16953357@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1871 bytes --]
Hi all,
The following commits are also in the arm-soc tree as different commits
(but the same patches):
0a0e8571837d ("ARM: dts: stm32: add vrefint calibration on stm32mp13")
2a47c4033e09 ("ARM: dts: stm32: add an extra pin map for USART1 on stm32h743"
3acfa4becfda ("arm64: dts: st: Add SPI NOR flash support on stm32mp257f-ev1 board")
3bd31eb4f6ee ("ARM: dts: stm32: add vrefint support to adc on stm32mp13")
3f70ddb86143 ("ARM: dts: stm32: add initial support for stm32mp157-ultra-fly-sbc board")
46e2ad9fd187 ("ARM: dts: stm32: add low power timer on STM32F746")
532c5a818d2e ("arm64: defconfig: enable STM32 LP timer clockevent driver")
7b6bbef62485 ("ARM: dts: stm32: support STM32h747i-disco board")
7b7b6bb0f98d ("dt-bindings: clock: stm32h7: rename USART{7,8}_CK to UART{7,8}_CK")
826e6fb26193 ("dt-bindings: vendor-prefixes: Add Ultratronik")
878dec8597d4 ("arm64: dts: st: Add OMM node on stm32mp251")
8b773be67b10 ("MAINTAINERS: Add entry for ULTRATRONIK BOARD SUPPORT")
8c18889c702d ("arm64: dts: st: use lptimer3 as tick broadcast source on stm32mp257f-ev1")
a4d2108a4b3f ("ARM: stm32: add a new SoC - STM32H747")
a09cdc01ad4a ("ARM: dts: stm32: add pin map for UART8 controller on stm32h743")
bf98eb91ac66 ("ARM: dts: stm32h7-pinctrl: add _a suffix to u[s]art_pins phandles")
caeec8e2b846 ("dt-bindings: arm: stm32: add compatible for stm32h747i-disco board")
dd9bfe13b47e ("ARM: dts: st: stm32: Align wifi node name with bindings")
df863325b92c ("arm64: dts: st: add low-power timer nodes on stm32mp251")
f069852c9b33 ("dt-bindings: arm: stm32: Document Ultratronik's Fly board DT binding")
f80958d949c3 ("arm64: dts: st: Add ospi port1 pinctrl entries in stm32mp25-pinctrl.dtsi")
fe8690b58efb ("ARM: dts: stm32: add uart8 node for stm32h743 MCU")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-05-22 1:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 1:38 Stephen Rothwell [this message]
2025-06-10 23:04 ` linux-next: duplicate patches in the stm32 tree Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
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-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=20250522113816.16953357@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 \
/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