From: Zongkun Lei <leizongkun@qq.com>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: Zongkun Lei <leizongkun@qq.com>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>, Peter Xu <peterx@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
Kairui Song <kasong@tencent.com>, Michal Hocko <mhocko@suse.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Hugh Dickins <hughd@google.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Zi Yan <ziy@nvidia.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/6] mm: swap support for hugetlb folios
Date: Tue, 29 Sep 2026 17:30:04 +0800 [thread overview]
Message-ID: <tencent_736FFBB76DA2EA0BF5E60B9BCFAAE9692707@qq.com> (raw)
In-Reply-To: <art0PItp9LoUXIcd@gremlin>
On Tue, 29 Sep 2026 09:18:51 +0100, Lorenzo Stoakes wrote:
> What David said - hugetlb is in freeze so we're unfortunately not
> interested in such a big change.
Understood -- my mistake was misreading the subsystem's direction:
from earlier list discussions I had concluded that keeping hugetlb's
reservation semantics intact was the bar, and designed the series
around that; I see now that the actual position is a broader feature
freeze. Thank you both for the straight answer.
> Also you somehow sent the cover letter and the patches separately.
My apologies for the mess. My SMTP provider (QQ) rewrites the
Message-ID header of outgoing mail but leaves In-Reply-To untouched,
so the patches reference a cover Message-ID that never reached the
list.
> ... triggered an AI detector script ...
Fair, and thank you for raising it openly. Full disclosure: I used
an LLM to help organise and polish the English of the cover letter
and the per-patch commit messages. It also reviewed the code, and
some fixes found during those reviews were applied with its help.
That said, I understand every line of the final code and can defend
all of it in as much detail as anyone wants. Going forward, any
submission from me will carry the disclosure tag that
Documentation/process/coding-assistants.html requires.
> ... we expect you to do smaller work before moving on to larger
> changes ...
Point taken, and it is fair. I will look for smaller mm work to
build that track record -- pointers to a good entry point are
welcome.
Thanks for the detailed reply, and for pointing me in the right
direction.
Zongkun
prev parent reply other threads:[~2026-09-29 9:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 7:53 Zongkun Lei
2026-09-29 8:02 ` David Hildenbrand (Arm)
2026-09-29 9:26 ` Zongkun Lei
2026-10-01 7:48 ` David Hildenbrand (Arm)
2026-09-29 8:18 ` Lorenzo Stoakes (ARM)
2026-09-29 9:30 ` Zongkun Lei [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=tencent_736FFBB76DA2EA0BF5E60B9BCFAAE9692707@qq.com \
--to=leizongkun@qq.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=peterx@redhat.com \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®