From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, timmurray@google.com,
surenb@google.com, mhocko@suse.com, hca@linux.ibm.com,
david@kernel.org, brauner@kernel.org
Subject: Re: + mm-process_mrelease-introduce-process_mrelease_reap_kill-flag.patch added to mm-new branch
Date: Fri, 15 May 2026 14:02:36 -0700 [thread overview]
Message-ID: <ageJ7IOUFPH6MW2D@google.com> (raw)
In-Reply-To: <20260512214249.53993C2BCB0@smtp.kernel.org>
On Tue, May 12, 2026 at 02:42:48PM -0700, Andrew Morton wrote:
>
> The patch titled
> Subject: mm: process_mrelease: introduce PROCESS_MRELEASE_REAP_KILL flag
> has been added to the -mm mm-new branch. Its filename is
> mm-process_mrelease-introduce-process_mrelease_reap_kill-flag.patch
>
> This patch will shortly appear at
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-process_mrelease-introduce-process_mrelease_reap_kill-flag.patch
>
> This patch will later appear in the mm-new branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>
> Note, mm-new is a provisional staging ground for work-in-progress
> patches, and acceptance into mm-new is a notification for others take
> notice and to finish up reviews. Please do not hesitate to respond to
> review feedback and post updated versions to replace or incrementally
> fixup patches in mm-new.
>
> The mm-new branch of mm.git is not included in linux-next
>
> If a few days of testing in mm-new is successful, the patch will me moved
> into mm.git's mm-unstable branch, which is included in linux-next
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
>
> The -mm tree is included into linux-next via various
> branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> and is updated there most days
>
> ------------------------------------------------------
> From: Minchan Kim <minchan@kernel.org>
> Subject: mm: process_mrelease: introduce PROCESS_MRELEASE_REAP_KILL flag
> Date: Mon, 11 May 2026 14:42:26 -0700
Andrew, can you drop this patch?
Following our discussion, I’ll rework the process_mrelease issue
by building on Jann's patch instead.
https://lore.kernel.org/linux-mm/ageHmE1QIzK4R3nO@google.com/
Thank you.
next prev parent reply other threads:[~2026-05-15 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 21:42 + mm-process_mrelease-introduce-process_mrelease_reap_kill-flag.patch added to mm-new branch Andrew Morton
2026-05-15 21:02 ` Minchan Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-30 14:43 Andrew Morton
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=ageJ7IOUFPH6MW2D@google.com \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@kernel.org \
--cc=hca@linux.ibm.com \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=surenb@google.com \
--cc=timmurray@google.com \
/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.