From: Andrew Morton <akpm@linux-foundation.org>
To: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
hughd@google.com, willy@infradead.org, ziy@nvidia.com,
david@kernel.org, lance.yang@linux.dev,
wangkefeng.wang@huawei.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "tmpfs: don't enable large folios if not supported"
Date: Mon, 11 May 2026 18:15:29 -0700 [thread overview]
Message-ID: <20260511181529.a099f05a9d96986d5e88a0ed@linux-foundation.org> (raw)
In-Reply-To: <b1302558-e5a0-4963-b9ed-533d35dea802@linux.alibaba.com>
On Tue, 12 May 2026 08:55:05 +0800 Baolin Wang <baolin.wang@linux.alibaba.com> wrote:
> >
> > Please let's not add new metadata without having told others what that
> > metadata means?
> >
> > "Fixes:" should be sufficient. I interpret Fixes: as "apply this to any
> > kernel which contains <that>". Is more needed?
>
> My concern is that if someone backports this patch to an older kernel
> version without also backporting commit 665575cff098b, it would cause a
> performance regression.
>
> Is there a good way to mark this kind of dependency on another patch?
Not that I know of. Has someone sent 665575cff098b to -stable
maintainers and asked them to treat it as Fixes: 5a90c155defa?
> But I've already described this potential dependency in the commit
> message, so I'm fine with just adding the "Fixes:" tag.
Yeah, I guess the supporting text will help clear confusion.
But you're right - our tooling should be able to express such things.
prev parent reply other threads:[~2026-05-12 1:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b2c7deee259a94b0d00a7c320d8d24d2c421f761.1776908112.git.baolin.wang@linux.alibaba.com>
2026-05-05 10:46 ` [PATCH] Revert "tmpfs: don't enable large folios if not supported" Lorenzo Stoakes
2026-05-05 10:47 ` Lorenzo Stoakes
2026-05-06 8:58 ` Baolin Wang
2026-05-11 12:03 ` Lorenzo Stoakes
2026-05-11 22:01 ` Andrew Morton
2026-05-12 0:55 ` Baolin Wang
2026-05-12 1:15 ` Andrew Morton [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=20260511181529.a099f05a9d96986d5e88a0ed@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=hughd@google.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=wangkefeng.wang@huawei.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