From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>, linux-mm@kvack.org
Subject: Re: mm.git review status at 7.0-rc6
Date: Wed, 1 Apr 2026 17:53:17 -0700 [thread overview]
Message-ID: <20260402005318.64637-1-sj@kernel.org> (raw)
In-Reply-To: <20260331213956.2f3925ff0dd12eabf55b7c37@linux-foundation.org>
On Tue, 31 Mar 2026 21:39:56 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
[...]
> People, please let's not see an enormous flood of patches the day after
> -rc1 is released? If you have new non-critical patches then it's best
> to send them out when they're ready rather than buffering them up.
> They won't be applied to mm.git and they may not get 100% attention but
> it's better this way - spread things out, at least give others a view
> of what's coming up.
Makes sense. I promised to not drop RFC for non-hotfixes til next -rc1 [1],
and was having a similar concern. So I will withdraw that and go back to the
normal mode.
[1] https://lore.kernel.org/20260322003459.86313-1-sj@kernel.org
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-04-02 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 4:39 mm.git review status at 7.0-rc6 Andrew Morton
2026-04-02 0:53 ` SeongJae Park [this message]
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=20260402005318.64637-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
/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