From: Lorenzo Stoakes <ljs@kernel.org>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Baolin Wang <baolin.wang@linux.alibaba.com>,
ranxiaokai627@163.com, hughd@google.com,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, ran.xiaokai@zte.com.cn,
"leitao@debian.org >> Breno Leitao" <leitao@debian.org>
Subject: Re: [PATCH 1/2] mm: huge_memory: refactor thpsize_shmem_enabled_store() with sysfs_match_string()
Date: Wed, 13 May 2026 10:40:13 +0100 [thread overview]
Message-ID: <agRG30FxrwP90l9_@lucifer> (raw)
In-Reply-To: <e80c7f34-40c1-4854-8f3a-2461022f86cc@kernel.org>
On Wed, May 13, 2026 at 11:38:21AM +0200, David Hildenbrand (Arm) wrote:
> On 5/13/26 11:03, Lorenzo Stoakes wrote:
> > +cc David also!
> >
> > Unfortunately we put some hugetlb logic in mm/shmem.c too which makes
> > get_maintainers.pl not do the right thing.
> >
> > I wonder if we should add mm/shmem.c to the THP section _also_ just to cover
> > this off?
>
> I'd rather not. Too much noise :)
Haha fair enough... maybe we should move this stuff to huge_memory.c or
something, but not sure if that makes sense.
Not a _hugely_ big deal though tbh!
>
> --
> Cheers,
>
> David
Cheers, Lorenzo
next prev parent reply other threads:[~2026-05-13 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 12:05 [PATCH 1/2] mm: huge_memory: refactor thpsize_shmem_enabled_store() with sysfs_match_string() ranxiaokai627
2026-05-12 12:05 ` [PATCH 2/2] mm: huge_memory: refactor thpsize_shmem_enabled_show() with helper arrays ranxiaokai627
2026-05-13 3:04 ` [PATCH 1/2] mm: huge_memory: refactor thpsize_shmem_enabled_store() with sysfs_match_string() Baolin Wang
2026-05-13 8:25 ` ranxiaokai627
2026-05-13 8:56 ` Breno Leitao
2026-05-13 9:03 ` Lorenzo Stoakes
2026-05-13 9:38 ` David Hildenbrand (Arm)
2026-05-13 9:40 ` Lorenzo Stoakes [this message]
2026-05-13 10:09 ` ranxiaokai627
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=agRG30FxrwP90l9_@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=hughd@google.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=ranxiaokai627@163.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.