From: Yury Norov <ynorov@nvidia.com>
To: Ryota Sakamoto <sakamo.ryota@gmail.com>
Cc: Yury Norov <yury.norov@gmail.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/tests: extend KUnit test for bitops with more cases
Date: Tue, 27 Jan 2026 08:26:10 -0500 [thread overview]
Message-ID: <aXi88qhW_Cgvk7fT@yury> (raw)
In-Reply-To: <20260123-kunit-bitops-new-tests-v1-1-47e516054738@gmail.com>
On Fri, Jan 23, 2026 at 12:40:41AM +0900, Ryota Sakamoto wrote:
> Extend a KUnit test suite for the bitops API to cover more APIs from
> include/asm-generic/bitops/instrumented-atomic.h.
>
> - change_bit()
> - test_and_set_bit()
> - test_and_clear_bit()
> - test_and_change_bit()
>
> Verified on x86_64, i386, and arm64 architectures.
>
> Sample KUnit output:
>
> KTAP version 1
> # Subtest: test_change_bit
> ok 1 BITOPS_4
> ok 2 BITOPS_7
> ok 3 BITOPS_11
> ok 4 BITOPS_31
> ok 5 BITOPS_88
> # test_change_bit: pass:5 fail:0 skip:0 total:5
> ok 2 test_change_bit
> KTAP version 1
> # Subtest: test_test_and_set_bit_test_and_clear_bit
> ok 1 BITOPS_4
> ok 2 BITOPS_7
> ok 3 BITOPS_11
> ok 4 BITOPS_31
> ok 5 BITOPS_88
> # test_test_and_set_bit_test_and_clear_bit: pass:5 fail:0 skip:0 total:5
> ok 3 test_test_and_set_bit_test_and_clear_bit
> KTAP version 1
> # Subtest: test_test_and_change_bit
> ok 1 BITOPS_4
> ok 2 BITOPS_7
> ok 3 BITOPS_11
> ok 4 BITOPS_31
> ok 5 BITOPS_88
> # test_test_and_change_bit: pass:5 fail:0 skip:0 total:5
> ok 4 test_test_and_change_bit
>
> Signed-off-by: Ryota Sakamoto <sakamo.ryota@gmail.com>
Applied, thanks!
prev parent reply other threads:[~2026-01-27 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 15:40 Ryota Sakamoto
2026-01-27 13:26 ` Yury Norov [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=aXi88qhW_Cgvk7fT@yury \
--to=ynorov@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=sakamo.ryota@gmail.com \
--cc=yury.norov@gmail.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®