From: Petr Mladek <pmladek@suse.com>
To: Tamir Duberstein <tamird@gmail.com>, Kees Cook <kees@kernel.org>
Cc: David Gow <davidgow@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v9 0/6] scanf: convert self-test to KUnit
Date: Fri, 14 Mar 2025 14:29:40 +0100 [thread overview]
Message-ID: <Z9QvRJE0Yun5mfsN@pathway.suse.cz> (raw)
In-Reply-To: <20250307-scanf-kunit-convert-v9-0-b98820fa39ff@gmail.com>
On Fri 2025-03-07 06:27:33, Tamir Duberstein wrote:
> This is one of just 3 remaining "Test Module" kselftests (the others
> being bitmap and printf), the rest having been converted to KUnit. In
> addition to the enclosed patch, please consider this an RFC on the
> removal of the "Test Module" kselftest machinery.
>
> Tamir Duberstein (6):
> scanf: implicate test line in failure messages
> scanf: remove redundant debug logs
> scanf: convert self-test to KUnit
> scanf: break kunit into test cases
Kees, could you please take the above 5 patches as well
via the tree moving the KUNIT tests to lib/tests ?
They seem to be ready for linux-next and the next merge window.
> scanf: tidy header `#include`s
This one is a bit controversial and might be added later.
> scanf: further break kunit into test cases
This one was just an attempt. But I personally think that
it is not worth it.
Best Regards,
Petr
next prev parent reply other threads:[~2025-03-14 13:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 11:27 [PATCH v9 0/6] scanf: convert self-test to KUnit Tamir Duberstein
2025-03-07 11:27 ` [PATCH v9 1/6] scanf: implicate test line in failure messages Tamir Duberstein
2025-03-07 11:27 ` [PATCH v9 2/6] scanf: remove redundant debug logs Tamir Duberstein
2025-03-07 11:27 ` [PATCH v9 3/6] scanf: convert self-test to KUnit Tamir Duberstein
2025-03-07 11:27 ` [PATCH v9 4/6] scanf: break kunit into test cases Tamir Duberstein
2025-03-14 12:55 ` Petr Mladek
2025-03-07 11:27 ` [PATCH v9 5/6] scanf: tidy header `#include`s Tamir Duberstein
2025-03-07 17:34 ` Andy Shevchenko
2025-03-07 17:39 ` Andy Shevchenko
2025-03-07 17:42 ` Tamir Duberstein
2025-03-14 13:04 ` Petr Mladek
2025-03-07 11:27 ` [PATCH v9 6/6] scanf: further break kunit into test cases Tamir Duberstein
2025-03-14 13:21 ` Petr Mladek
2025-03-14 13:27 ` Tamir Duberstein
2025-03-14 13:29 ` Petr Mladek [this message]
2025-03-14 20:45 ` [PATCH v9 0/6] scanf: convert self-test to KUnit Kees Cook
2025-03-14 20:50 ` Tamir Duberstein
2025-03-17 10:34 ` Petr Mladek
2025-03-14 20:59 ` (subset) " Kees Cook
2025-03-14 21:31 ` Tamir Duberstein
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=Z9QvRJE0Yun5mfsN@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davidgow@google.com \
--cc=geert@linux-m68k.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=shuah@kernel.org \
--cc=tamird@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