From: Drew Fustini <drew@pdp7.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul@pwsan.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the risc-v tree
Date: Thu, 30 Jan 2025 18:18:32 -0800 [thread overview]
Message-ID: <Z5wy+NosgbxYk3fN@x1> (raw)
In-Reply-To: <20250131075413.6fc6c272@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
On Fri, Jan 31, 2025 at 07:54:13AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> 0207244ea0e7 ("riscv: defconfig: enable pinctrl and dwmac support for TH1520")
>
> --
> Cheers,
> Stephen Rothwell
Sorry about that. I did a RESEND on December 15th [1] which Conor took
on December 16th [2]. I did not realize when I resent it that Palmer
had already commited it on December 11th [3].
I'm not sure what the correct resolution is. Drop 0207244ea0e7 from
riscv/for-next?
Thanks,
Drew
[1] https://lore.kernel.org/all/20241216003114.326129-1-drew@pdp7.com
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/riscv/configs?id=e7177ecdd2b73de4e19a02794d29e6c5f06728ab
[3] https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/commit/arch/riscv/configs?h=for-next&id=0207244ea0e7fcf45e68e24b0fffe964624a22ef
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-01-31 2:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 20:54 linux-next: duplicate patch in the risc-v tree Stephen Rothwell
2025-01-31 2:18 ` Drew Fustini [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-11 21:36 Stephen Rothwell
2024-07-25 21:59 Stephen Rothwell
2024-07-26 22:55 ` Palmer Dabbelt
2024-04-28 21:35 Stephen Rothwell
2024-04-28 21:55 ` Palmer Dabbelt
2024-04-10 22:06 Stephen Rothwell
2024-04-11 19:57 ` Palmer Dabbelt
2023-11-02 20:58 Stephen Rothwell
2023-11-02 21:07 ` Palmer Dabbelt
2023-10-29 23:12 Stephen Rothwell
2023-08-30 22:01 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=Z5wy+NosgbxYk3fN@x1 \
--to=drew@pdp7.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul@pwsan.com \
--cc=sfr@canb.auug.org.au \
/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