From: Sasha Levin <sashal@kernel.org>
To: David Hildenbrand <david@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: add CONFIG_DEBUG_FS to the config fragment
Date: Fri, 6 Nov 2026 13:52:18 -0500 [thread overview]
Message-ID: <20261106185218.1766376-1-sashal@kernel.org> (raw)
In-Reply-To: <179397467526.9397.17872200045070830000.b4-ty@b4>
On Fri, 06 Nov 2026 15:17:55 +0100, David Hildenbrand wrote:
>[1/1] selftests/mm: add CONFIG_DEBUG_FS to the config fragment
> https://git.kernel.org/mm/core/c/31ea5515
Thanks! It looks like this one landed on both thp-7.5.misc and
core-7.5.misc:
31ea5515bf59 ("selftests/mm: add CONFIG_DEBUG_FS to the config fragment")
194b63198811 ("selftests/mm: add CONFIG_DEBUG_FS to the config fragment")
Was the thp-7.5.misc one meant to be the split_huge_page_test skip patch?
https://lore.kernel.org/all/20261105030242.1241448-1-sashal@kernel.org/
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-11-06 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 3:02 [PATCH] selftests/mm: skip split_huge_page_test without the split_huge_pages file Sasha Levin
2026-11-05 11:49 ` Kiryl Shutsemau
2026-11-05 15:19 ` Zi Yan
2026-11-05 15:51 ` David Hildenbrand (Arm)
2026-11-05 17:18 ` [PATCH] selftests/mm: add CONFIG_DEBUG_FS to the config fragment Sasha Levin
2026-11-05 17:21 ` Zi Yan
2026-11-05 17:53 ` David Hildenbrand (Arm)
2026-11-06 14:17 ` David Hildenbrand
2026-11-06 14:17 ` David Hildenbrand
2026-11-06 18:52 ` Sasha Levin [this message]
2026-11-06 21:32 ` David Hildenbrand (Arm)
2026-11-06 2:37 ` [PATCH] selftests/mm: skip split_huge_page_test without the split_huge_pages file Baolin Wang
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=20261106185218.1766376-1-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.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
all inboxes | Powered by JetHome®