From: Disha Goel <disgoel@linux.ibm.com>
To: Christian Brauner <brauner@kernel.org>
Cc: shuah@kernel.org, wenyang.linux@foxmail.com,
akpm@linux-foundation.org, jlayton@kernel.org, jack@suse.cz,
djwong@kernel.org, aleksa@amutable.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] selftests/filesystems: fix missing and stale TARGETS entries
Date: Mon, 31 Aug 2026 15:16:45 +0530 [thread overview]
Message-ID: <cecdc333-f58a-4e8b-a3f5-774fd0e69cf7@linux.ibm.com> (raw)
In-Reply-To: <20260706-geerntet-neonlicht-liege-d005ee1904b3@brauner>
Gentle ping — is this patch merged or queued for a future merge window.
On 06/07/26 6:40 pm, Christian Brauner wrote:
>> filesystems/eventfd, filesystems/open_tree_ns and filesystems/xattr
>> were never added to TARGETS when introduced. filesystems/openat2 was
>> moved from selftests/openat2/ but the TARGETS entry was never updated,
>> leaving a stale entry pointing at a directory that no longer exists.
>>
>> Fix this by adding the four missing subdirectories to TARGETS and
>> removing the stale openat2 entry.
>>
>> Fixes: 7c37857fc23a ("selftests: add eventfd selftests")
>> Fixes: b8f7622aa6e3 ("selftests/open_tree: add OPEN_TREE_NAMESPACE tests")
>> Fixes: 7e28fef5d4db ("selftests/xattr: path-based AF_UNIX socket xattr tests")
>> Fixes: fe087927046c ("selftests: move openat2 tests to selftests/filesystems/")
>> Signed-off-by: Disha Goel <disgoel@linux.ibm.com>
>
> Seems fine,
> Reviewed-by: Christian Brauner (Amutable) <brauner@kernel.org>
>
--
Regards,
Disha
next prev parent reply other threads:[~2026-08-31 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 15:07 [PATCH] selftests/filesystems: fix missing and stale TARGETS entries Disha Goel
2026-07-06 13:10 ` Christian Brauner
2026-08-31 9:46 ` Disha Goel [this message]
2026-09-03 2:17 ` Andrew Morton
2026-09-04 10:27 ` Christian Brauner
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=cecdc333-f58a-4e8b-a3f5-774fd0e69cf7@linux.ibm.com \
--to=disgoel@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aleksa@amutable.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=wenyang.linux@foxmail.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.