From: Yury Norov <yury.norov@gmail.com>
To: Sander Vanheule <sander@svanheule.net>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Brendan Higgins" <brendan.higgins@linux.dev>,
"David Gow" <davidgow@google.com>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
"Maíra Canal" <mairacanal@riseup.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] cpumask: KUnit test suite fixes and improvements
Date: Wed, 24 Aug 2022 09:09:18 -0700 [thread overview]
Message-ID: <YwZNLoHtm7b6t4y2@yury-laptop> (raw)
In-Reply-To: <cover.1661234636.git.sander@svanheule.net>
On Tue, Aug 23, 2022 at 08:12:17AM +0200, Sander Vanheule wrote:
> This series fixes the reported issues, and implements the suggested
> improvements, for the version of the cpumask tests [1] that was merged
> with commit c41e8866c28c ("lib/test: introduce cpumask KUnit test
> suite").
>
> These changes include fixes for the tests, and better alignment with the
> KUnit style guidelines.
Applied in bitmap-for-next.
Thanks,
Yury
> [1] https://lore.kernel.org/all/85217b5de6d62257313ad7fde3e1969421acad75.1659077534.git.sander@svanheule.net/
>
> Changes since v2:
> Link: https://lore.kernel.org/lkml/cover.1661007338.git.sander@svanheule.net/
> - Update commit message of "lib/test_cpumask: drop cpu_possible_mask
> full test"
> - Use *_MSG() macros to only print mask contents on failure
>
> Changes since v1:
> Link: https://lore.kernel.org/lkml/cover.1660068429.git.sander@svanheule.net/
> - Collect tags
> - Rewrite commit message of "lib/test_cpumask: drop cpu_possible_mask
> full test"
> - Also CC KUnit mailing list
>
> Sander Vanheule (5):
> lib/test_cpumask: drop cpu_possible_mask full test
> lib/test_cpumask: fix cpu_possible_mask last test
> lib/test_cpumask: follow KUnit style guidelines
> lib/cpumask_kunit: log mask contents
> lib/cpumask_kunit: add tests file to MAINTAINERS
>
> MAINTAINERS | 1 +
> lib/Kconfig.debug | 7 +++-
> lib/Makefile | 2 +-
> lib/{test_cpumask.c => cpumask_kunit.c} | 52 +++++++++++++++----------
> 4 files changed, 38 insertions(+), 24 deletions(-)
> rename lib/{test_cpumask.c => cpumask_kunit.c} (58%)
>
> --
> 2.37.2
prev parent reply other threads:[~2022-08-24 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 6:12 [PATCH v3 0/5] cpumask: KUnit test suite fixes and improvements Sander Vanheule
2022-08-23 6:12 ` [PATCH v3 1/5] lib/test_cpumask: drop cpu_possible_mask full test Sander Vanheule
2022-08-23 6:12 ` [PATCH v3 2/5] lib/test_cpumask: fix cpu_possible_mask last test Sander Vanheule
2022-08-23 6:12 ` [PATCH v3 3/5] lib/test_cpumask: follow KUnit style guidelines Sander Vanheule
2022-08-23 6:12 ` [PATCH v3 4/5] lib/cpumask_kunit: log mask contents Sander Vanheule
2022-08-23 6:12 ` [PATCH v3 5/5] lib/cpumask_kunit: add tests file to MAINTAINERS Sander Vanheule
2022-08-24 16:09 ` 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=YwZNLoHtm7b6t4y2@yury-laptop \
--to=yury.norov@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mairacanal@riseup.net \
--cc=sander@svanheule.net \
/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