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: Fri, 13 Jan 2023 09:29:24 -0700 [thread overview]
Message-ID: <87y1q6qty3.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230113111102.22a27ae3@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> The following commit is also in the mm-hotfixes tree as a different commit
> (but the same patch):
>
> ded24dfdddd1 ("Docs/admin-guide/mm/zswap: remove zsmalloc's lack of writeback warning")
>
> (commit 1beb8ae302a0 in the mm-hotfixes tree).
Offending patch removed.
Thanks,
jon
next prev parent reply other threads:[~2023-01-13 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 0:11 linux-next: duplicate patch in the jc_docs tree Stephen Rothwell
2023-01-13 16:29 ` Jonathan Corbet [this message]
2023-04-11 5:16 Stephen Rothwell
2023-04-11 22:16 ` Jonathan Corbet
2024-02-12 23:37 Stephen Rothwell
2024-02-12 23:41 ` Jonathan Corbet
2024-02-13 4:49 Stephen Rothwell
2024-02-13 14:36 ` 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=87y1q6qty3.fsf@meer.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).