From: Sasha Levin <sashal@kernel.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Lorenzo Stoakes <ljs@kernel.org>, Barry Song <baohua@kernel.org>,
David Hildenbrand <david@kernel.org>, Dev Jain <dev.jain@arm.com>,
Lance Yang <lance.yang@linux.dev>,
"Liam R . Howlett" <liam@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
Ryan Roberts <ryan.roberts@arm.com>,
William Kucharski <william.kucharski@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Zi Yan <ziy@nvidia.com>
Subject: Re: [PATCH 6.6.y] mm/huge_memory: use folio's memcg inside __folio_split()
Date: Mon, 14 Sep 2026 22:03:34 -0400 [thread overview]
Message-ID: <daily-reply-0018-re-huge-memory-folio-split-6-6@kernel.org> (raw)
In-Reply-To: <DLDJWF5NE46Z.3JBTVOKAYOYGU@nvidia.com>
> Done. See https://lore.kernel.org/all/20260912182926.1326147-1-ziy@nvidia.com/
Queued for 6.12 and 6.6, thanks.
> BTW, I see you also sent one[1], but it seems that it is using a
> non-existing get_mem_cgroup_from_folio(). What is that for? Thanks.
That one was generated against a tree that has the helper and should not
have gone out for 6.6.y. Please ignore it, yours is what is queued.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-09-15 2:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 10:46 FAILED: patch "[PATCH] mm/huge_memory: use folio's memcg inside __folio_split()" failed to apply to 6.6-stable tree gregkh
2026-09-04 2:26 ` [PATCH 6.6.y] mm/huge_memory: use folio's memcg inside __folio_split() Zi Yan
2026-09-06 13:33 ` Sasha Levin
2026-09-06 22:46 ` Zi Yan
2026-09-08 0:53 ` Sasha Levin
2026-09-10 19:23 ` Johannes Weiner
2026-09-12 15:26 ` Sasha Levin
2026-09-12 18:31 ` Zi Yan
2026-09-15 2:03 ` Sasha Levin [this message]
2026-09-04 2:36 ` Sasha Levin
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=daily-reply-0018-re-huge-memory-folio-split-6-6@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=ljs@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=stable@vger.kernel.org \
--cc=william.kucharski@oracle.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