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: linux-next: duplicate patches in the stm32 tree
Date: Tue, 30 Apr 2024 11:04:28 +1000 [thread overview]
Message-ID: <20240430110428.30432b2f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]
Hi all,
The following commits are also in the arm-soc tree as different
commits (but the same patches):
0087ca056c73 ("arm64: dts: st: add all 8 i2c nodes on stm32mp251")
2886ab7437de ("arm64: dts: st: add rcc support for STM32MP25")
385ca8e3841f ("arm64: dts: st: add spi3 / spi8 properties on stm32mp257f-ev1"
)
3e7d579c9fca ("ARM: dts: stm32: add ETZPC as a system bus for STM32MP15x boar
ds")
4ef09379d765 ("arm64: dts: st: add i2c2 / i2c8 properties on stm32mp257f-ev1"
)
5e6b388d7bcb ("ARM: dts: stm32: move can3 node from stm32f746 to stm32f769")
7442597f90ba ("arm64: dts: st: add i2c2/i2c8 pins for stm32mp25")
7c12d95564a2 ("ARM: dts: stm32: add LTDC pinctrl on STM32MP13x SoC family")
7c3d4f99a920 ("ARM: dts: stm32: put ETZPC as an access controller for STM32MP
15x boards")
808691f7389d ("media: dt-bindings: add access-controllers to STM32MP25 video
codecs")
881bccce217e ("ARM: dts: stm32: add LTDC support for STM32MP13x SoC family")
8fe31699b83d ("bus: stm32_firewall: fix off by one in stm32_firewall_get_firewall()")
9e716b41a2b5 ("arm64: dts: st: add RIFSC as an access controller for STM32MP25x boards")
a012bd75abf6 ("ARM: dts: stm32: enable display support on stm32mp135f-dk board")
aee0ce48516c ("arm64: dts: st: add spi3/spi8 pins for stm32mp25")
be62e9c0c3fc ("bus: etzpc: introduce ETZPC firewall controller driver")
c7f2f2c0ace8 ("ARM: dts: stm32: add heartbeat led for stm32mp157c-ed1")
cab43766e000 ("ARM: dts: stm32: add ETZPC as a system bus for STM32MP13x boards")
d3740a9fd78c ("dt-bindings: display: simple: allow panel-common properties")
dccdbccb7045 ("arm64: dts: st: correct masks for GIC PPI interrupts on stm32mp25")
de9b447d5678 ("ARM: dts: stm32: put ETZPC as an access controller for STM32MP13x boards")
ede58756bbe5 ("arm64: dts: st: add all 8 spi nodes on stm32mp251")
f798f7079233 ("ARM: dts: stm32: add PWR regulators support on stm32mp131")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-04-30 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 1:04 Stephen Rothwell [this message]
2024-05-13 22:33 ` linux-next: duplicate patches in the stm32 tree Stephen Rothwell
2024-05-14 23:54 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
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=20240430110428.30432b2f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexandre.torgue@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).