From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Joel Stanley <joel@jms•id.au>
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 aspeed tree
Date: Thu, 5 Jan 2023 08:33:49 +1100 [thread overview]
Message-ID: <20230105083349.67f21dc2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
Hi all,
The following commits already exist in Linus Torvald's tree as different
commits (but the same patches):
220a041d4cca ("ARM: dts: nuvoton,wpcm450-supermicro-x9sci-ln4f: Add GPIO line names")
7996185ce194 ("ARM: dts: nuvoton: Remove bogus unit addresses from fixed-parti
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-01-04 21:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 21:33 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-01 21:47 linux-next: duplicate patches in the aspeed tree Stephen Rothwell
2023-08-15 1:41 Stephen Rothwell
2023-08-18 2:19 ` Joel Stanley
2023-08-18 3:21 ` Stephen Rothwell
2025-05-22 1:30 Stephen Rothwell
2025-05-22 1:40 ` 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=20230105083349.67f21dc2@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=joel@jms$(echo .)id.au \
--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