From: Christian Brauner <brauner@kernel.org>
To: Aleksa Sarai <cyphar@cyphar.com>
Cc: Aleksa Sarai <aleksa@amutable.com>, Shuah Khan <shuah@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 0/3] selftests: openat2: migrate to kselftests harness
Date: Tue, 7 Apr 2026 12:31:55 +0200 [thread overview]
Message-ID: <20260407-eskapaden-neuplanung-16ec00fcae1b@brauner> (raw)
In-Reply-To: <2026-03-31-somber-private-crew-movie-exaY9q@cyphar.com>
On Wed, Apr 01, 2026 at 02:10:16AM +1100, Aleksa Sarai wrote:
> On 2026-03-31, Christian Brauner <brauner@kernel.org> wrote:
> > On Wed, Apr 01, 2026 at 12:43:30AM +1100, Aleksa Sarai wrote:
> > > These tests were written in the early days of selftests' TAP support,
> > > the more modern kselftest harness is much easier to follow and maintain.
> > > The actual contents of the tests are unchanged by this change.
> > >
> > > Signed-off-by: Aleksa Sarai <aleksa@amutable.com>
> > > ---
> >
> > Looks all good to me. Do you want to maybe migrate the tests to the
> > filesystems/ subfolder as well?
>
> Good point, I'll move it over in v2.
Thank you!
prev parent reply other threads:[~2026-04-07 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 13:43 [PATCH 0/3] selftests: openat2: migrate to kselftests harness Aleksa Sarai
2026-03-31 13:43 ` [PATCH 1/3] selftests: openat2: move helpers to header Aleksa Sarai
2026-03-31 13:43 ` [PATCH 2/3] selftests: openat2: switch from custom ARRAY_LEN to ARRAY_SIZE Aleksa Sarai
2026-03-31 13:43 ` [PATCH 3/3] selftests: openat2: migrate to kselftest harness Aleksa Sarai
2026-03-31 14:27 ` [PATCH 0/3] selftests: openat2: migrate to kselftests harness Christian Brauner
2026-03-31 15:10 ` Aleksa Sarai
2026-04-07 10:31 ` Christian Brauner [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=20260407-eskapaden-neuplanung-16ec00fcae1b@brauner \
--to=brauner@kernel.org \
--cc=aleksa@amutable.com \
--cc=cyphar@cyphar.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
/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