From: Wen Yang <wen.yang@linux.dev>
To: Ryan Chung <seokwoo.chung130@gmail.com>, shuah@kernel.org
Cc: akpm@linux-foundation.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/eventfd: correct test name and improve messages
Date: Wed, 14 May 2025 00:12:17 +0800 [thread overview]
Message-ID: <b728052c-a5c0-490a-ac4d-64ea43c3e35d@linux.dev> (raw)
In-Reply-To: <20250513074411.6965-1-seokwoo.chung130@gmail.com>
Thanks.
Reviewed-by: Wen Yang <wen.yang@linux.dev>
--
Best wishes,
Wen
On 2025/5/13 15:44, Ryan Chung wrote:
> - Rename test from to
>
> - Make the RDWR‐flag comment declarative:
> “The kernel automatically adds the O_RDWR flag.”
> - Update semaphore‐flag failure message to:
> “eventfd semaphore flag check failed: …”
>
> Signed-off-by: Ryan Chung <seokwoo.chung130@gmail.com>
> ---
> tools/testing/selftests/filesystems/eventfd/eventfd_test.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/tools/testing/selftests/filesystems/eventfd/eventfd_test.c b/tools/testing/selftests/filesystems/eventfd/eventfd_test.c
> index 85acb4e3ef00..72d51ad0ee0e 100644
> --- a/tools/testing/selftests/filesystems/eventfd/eventfd_test.c
> +++ b/tools/testing/selftests/filesystems/eventfd/eventfd_test.c
> @@ -50,7 +50,7 @@ TEST(eventfd_check_flag_rdwr)
> ASSERT_GE(fd, 0);
>
> flags = fcntl(fd, F_GETFL);
> - // since the kernel automatically added O_RDWR.
> + // The kernel automatically adds the O_RDWR flag.
> EXPECT_EQ(flags, O_RDWR);
>
> close(fd);
> @@ -85,7 +85,7 @@ TEST(eventfd_check_flag_nonblock)
> close(fd);
> }
>
> -TEST(eventfd_chek_flag_cloexec_and_nonblock)
> +TEST(eventfd_check_flag_cloexec_and_nonblock)
> {
> int fd, flags;
>
> @@ -178,8 +178,7 @@ TEST(eventfd_check_flag_semaphore)
> // The semaphore could only be obtained from fdinfo.
> ret = verify_fdinfo(fd, &err, "eventfd-semaphore: ", 19, "1\n");
> if (ret != 0)
> - ksft_print_msg("eventfd-semaphore check failed, msg: %s\n",
> - err.msg);
> + ksft_print_msg("eventfd semaphore flag check failed: %s\n", err.msg);
> EXPECT_EQ(ret, 0);
>
> close(fd);
next prev parent reply other threads:[~2025-05-13 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 7:44 [PATCH] selftests/eventfd: correct test name and improve messages Ryan Chung
2025-05-13 16:12 ` Wen Yang [this message]
2025-05-22 21:47 ` Shuah Khan
2025-05-25 3:54 ` Ryan Chung
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=b728052c-a5c0-490a-ac4d-64ea43c3e35d@linux.dev \
--to=wen.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=seokwoo.chung130@gmail.com \
--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 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.