public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Alexandre Torgue <alexandre.torgue@st•com>
Cc: 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: Tue, 6 May 2025 07:44:52 +1000	[thread overview]
Message-ID: <20250506074452.65f4e0af@canb.auug.org.au> (raw)
In-Reply-To: <20250501113753.53f6fc88@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

Hi all,

On Thu, 1 May 2025 11:37:53 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> The following commits are also in the arm-soc-fixes tree as different
> commits (but the same patches):
> 
>   0530a74f3f43 ("arm64: dts: st: Use 128kB size for aliased GIC400 register access on stm32mp23 SoCs")
>   6485975d7832 ("arm64: dts: st: Adjust interrupt-controller for stm32mp23 SoCs")
>   635ff238ff7b ("arm64: dts: st: Use 128kB size for aliased GIC400 register access on stm32mp21 SoCs")
>   2ae67a2e7e4f ("arm64: dts: st: Adjust interrupt-controller for stm32mp21 SoCs")
>   97d0a619e248 ("arm64: dts: st: Use 128kB size for aliased GIC400 register access on stm32mp25 SoCs")
>   e5694384b07d ("arm64: dts: st: Adjust interrupt-controller for stm32mp25 SoCs")
> 
> These are commits
> 
>   2ef5c66cba61 ("arm64: dts: st: Use 128kB size for aliased GIC400 register access on stm32mp23 SoCs")
>   3a1e1082097b ("arm64: dts: st: Adjust interrupt-controller for stm32mp23 SoCs")
>   1bc229e9bb9c ("arm64: dts: st: Use 128kB size for aliased GIC400 register access on stm32mp21 SoCs")
>   02dc83f09c72 ("arm64: dts: st: Adjust interrupt-controller for stm32mp21 SoCs")
>   06c231fe953a ("arm64: dts: st: Use 128kB size for aliased GIC400 register access on stm32mp25 SoCs")
>   de2b2107d5a4 ("arm64: dts: st: Adjust interrupt-controller for stm32mp25 SoCs")
> 
> in the arm-soc-fixes tree.

These letter commits are now in Linus' tree.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2025-05-05 21:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-01  1:37 linux-next: duplicate patches in the stm32 tree Stephen Rothwell
2025-05-05 21:44 ` 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-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=20250506074452.65f4e0af@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