From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Chunwei Chen <david.chen@nutanix•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 mm-hotfixes tree
Date: Tue, 14 Feb 2023 11:09:54 +1100 [thread overview]
Message-ID: <20230214110954.18874441@canb.auug.org.au> (raw)
In-Reply-To: <20230213142953.9c62494f0db76ba0f8af6ad5@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
Hi Andrew,
On Mon, 13 Feb 2023 14:29:53 -0800 Andrew Morton <akpm@linux-foundation•org> wrote:
>
> yup, thanks. I've made a note not to send this upstream. But I'll
> keep it around in mm-hotfixes-unstable for a while so that users of the
> 6.2-rc4 based mm.git trees have it.
No worries, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-02-14 0:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 21:00 linux-next: duplicate patch in the mm-hotfixes tree Stephen Rothwell
2023-02-13 21:54 ` Stephen Rothwell
2023-02-13 22:29 ` Andrew Morton
2023-02-14 0:09 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-27 1:28 Stephen Rothwell
2023-03-13 21:24 Stephen Rothwell
2023-03-15 2:13 ` Stephen Rothwell
2023-06-07 22:47 Stephen Rothwell
2023-10-02 20:47 Stephen Rothwell
2024-04-21 22:10 Stephen Rothwell
2024-08-14 22:19 Stephen Rothwell
2024-08-18 21:58 Stephen Rothwell
2024-10-21 20:56 Stephen Rothwell
2024-11-07 21:32 Stephen Rothwell
2025-01-07 6:08 Stephen Rothwell
2025-09-07 21:53 Stephen Rothwell
2025-10-24 4:31 Stephen Rothwell
2025-11-24 20:37 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=20230214110954.18874441@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=david.chen@nutanix$(echo .)com \
--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