From: Andrew Morton <akpm@linux-foundation.org>
To: Lance Yang <lance.yang@linux.dev>
Cc: ziy@nvidia.com, david@kernel.org, willy@infradead.org,
songliubraving@fb.com, clm@fb.com, dsterba@suse.com,
viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
ljs@kernel.org, baolin.wang@linux.alibaba.com,
Liam.Howlett@oracle.com, npache@redhat.com, ryan.roberts@arm.com,
dev.jain@arm.com, baohua@kernel.org, vbabka@kernel.org,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
shuah@kernel.org, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v5 04/14] mm/khugepaged: remove READ_ONLY_THP_FOR_FS check in hugepage_enabled()
Date: Fri, 8 May 2026 11:54:03 -0700 [thread overview]
Message-ID: <20260508115403.055ea15a6852bacf864b7ad8@linux-foundation.org> (raw)
In-Reply-To: <20260507044938.12529-1-lance.yang@linux.dev>
On Thu, 7 May 2026 12:49:38 +0800 Lance Yang <lance.yang@linux.dev> wrote:
> I just noticed that mm-new commit 83f151d1f7e3[1] links to this patch:
>
> Link: https://lore.kernel.org/20260429152924.727124-5-ziy@nvidia.com
>
> but the applied commit only has the include/linux/shmem_fs.h hunk ...
> The mm/khugepaged.c hunk seems missing.
Thanks, fixed.
> Was this dropped unintentionally?
Nope. Collateral damage when I was trying to figure out how to drop
"khugepaged: mTHP support, v16".
next prev parent reply other threads:[~2026-05-08 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260429152924.727124-5-ziy@nvidia.com>
2026-05-07 4:49 ` [PATCH v5 04/14] mm/khugepaged: remove READ_ONLY_THP_FOR_FS check in hugepage_enabled() Lance Yang
2026-05-08 18:54 ` Andrew Morton [this message]
2026-05-11 7:15 ` Lance Yang
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=20260508115403.055ea15a6852bacf864b7ad8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=clm@fb.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=dsterba@suse.com \
--cc=jack@suse.cz \
--cc=lance.yang@linux.dev \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=songliubraving@fb.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--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