public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Lorenzo Stoakes <ljs@kernel.org>
Cc: akpm@linux-foundation.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: Wed, 6 May 2026 16:58:20 +0800	[thread overview]
Message-ID: <b496c241-006f-41ea-a398-0e0b7c7e8472@linux.alibaba.com> (raw)
In-Reply-To: <afnKpTo4cwh9LtPU@lucifer>



On 5/5/26 6:47 PM, Lorenzo Stoakes wrote:
> On Tue, May 05, 2026 at 11:46:11AM +0100, Lorenzo Stoakes wrote:
>> Acked-by: Lorenzo Stoakes <ljs@kernel.org>
>>
>> As David asked, should we have a Fixes tag? What about cc: stable?

Sure. But this fix tag depends on the commit 665575cff098b, so the fixes 
tag should be:

Fixes: 5a90c155defa ("tmpfs: don't enable large folios if not supported")
Depends-on: 665575cff098b ("filemap: move prefaulting out of hot write 
path").

I don't think we need to cc stable, as it doesn't appear to cause any 
serious issues currently.

      reply	other threads:[~2026-05-06  8:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  1:41 [PATCH] Revert "tmpfs: don't enable large folios if not supported" Baolin Wang
2026-04-23  2:37 ` Zi Yan
2026-04-23  2:46 ` Kefeng Wang
2026-04-23  2:57 ` Lance Yang
2026-04-23 13:20 ` David Hildenbrand (Arm)
2026-04-26  5:55   ` Baolin Wang
2026-05-05 10:46 ` Lorenzo Stoakes
2026-05-05 10:47   ` Lorenzo Stoakes
2026-05-06  8:58     ` Baolin Wang [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=b496c241-006f-41ea-a398-0e0b7c7e8472@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --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