From: Jonathan Corbet <corbet@lwn.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>
Cc: 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 jc_docs tree
Date: Wed, 07 May 2025 00:51:56 -0600 [thread overview]
Message-ID: <87bjs4vroz.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250507111956.69847ed6@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> The following commit is also in the mm-unstable tree as a different commit
> (but the same patch):
>
> 98d2ea56614b ("docs/mm/damon/design: Fix spelling mistake")
>
> This is commit
>
> 7368fcda3f61 ("docs/mm/damon/design: fix spelling mistake")
>
> in the mm-unstable tree.
Yup, I'll soon drop mine.
Thanks,
jon
next prev parent reply other threads:[~2025-05-07 6:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 1:19 linux-next: duplicate patch in the jc_docs tree Stephen Rothwell
2025-05-07 6:51 ` Jonathan Corbet [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-13 1:25 Stephen Rothwell
2025-05-07 1:18 Stephen Rothwell
2025-02-19 0:32 Stephen Rothwell
2025-02-14 5:10 Stephen Rothwell
2025-02-14 13:20 ` Palmer Dabbelt
2025-01-17 1:02 Stephen Rothwell
2024-10-14 2:03 Stephen Rothwell
2024-10-14 14:52 ` Jonathan Corbet
2024-02-13 4:49 Stephen Rothwell
2024-02-13 14:36 ` Jonathan Corbet
2024-02-12 23:37 Stephen Rothwell
2024-02-12 23:41 ` Jonathan Corbet
2023-04-11 5:16 Stephen Rothwell
2023-04-11 22:16 ` Jonathan Corbet
2023-01-13 0:11 Stephen Rothwell
2023-01-13 16:29 ` Jonathan Corbet
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=87bjs4vroz.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.