From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Joel Stanley <joel@jms•id.au>, Arnd Bergmann <arnd@arndb•de>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
ARM <linux-arm-kernel@lists•infradead.org>
Subject: Re: linux-next: duplicate patches in the aspeed tree
Date: Thu, 22 May 2025 11:40:14 +1000 [thread overview]
Message-ID: <20250522114014.5743b499@canb.auug.org.au> (raw)
In-Reply-To: <20250522113033.066d7216@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 529 bytes --]
Hi all,
[cc arm-soc]
On Thu, 22 May 2025 11:30:33 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Hi all,
>
> The following commits are also in the arm-soc tree as different commits
> (but the same patches):
>
> 28fe68179368 ("arm64: dts: nuvoton: Add pinctrl")
> 82f50ddf894e ("ARM: aspeed: Don't select SRAM")
> 856d11d63f85 ("soc: aspeed: lpc: Fix impossible judgment condition")
> f3089a4fc247 ("soc: aspeed: Add NULL check in aspeed_lpc_enable_snoop()")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-05-22 1:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 1:30 linux-next: duplicate patches in the aspeed tree Stephen Rothwell
2025-05-22 1:40 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-15 1:41 Stephen Rothwell
2023-08-18 2:19 ` Joel Stanley
2023-08-18 3:21 ` Stephen Rothwell
2023-02-01 21:47 Stephen Rothwell
2023-01-04 21:33 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=20250522114014.5743b499@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=arnd@arndb$(echo .)de \
--cc=joel@jms$(echo .)id.au \
--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