From: Randy Dunlap <rdunlap@infradead.org>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>,
linux-fsdevel@vger.kernel.org
Cc: kernel@collabora.com, krisman@collabora.com
Subject: Re: [PATCH] Implement utf8 unit tests as a kunit test suite.
Date: Wed, 15 Apr 2020 09:19:57 -0700 [thread overview]
Message-ID: <31317125-42d6-3306-aa06-955eebb07623@infradead.org> (raw)
In-Reply-To: <20200415082826.19325-1-ricardo.canuelo@collabora.com>
Hi,
On 4/15/20 1:28 AM, Ricardo Cañuelo wrote:
> diff --git a/fs/unicode/Kconfig b/fs/unicode/Kconfig
> index 2c27b9a5cd6c..734c25920750 100644
> --- a/fs/unicode/Kconfig
> +++ b/fs/unicode/Kconfig
> @@ -8,7 +8,19 @@ config UNICODE
> Say Y here to enable UTF-8 NFD normalization and NFD+CF casefolding
> support.
>
> -config UNICODE_NORMALIZATION_SELFTEST
> - tristate "Test UTF-8 normalization support"
> - depends on UNICODE
> +config UNICODE_KUNIT_TESTS
> + bool "Kunit tests for UTF-8 support"
> + depends on UNICODE && KUNIT
> default n
> + help
> + This builds the ext4 KUnit tests.
ext4??
> +
> + KUnit tests run during boot and output the results to the debug log
> + in TAP format (http://testanything.org/). Only useful for kernel devs
> + running KUnit test harness and are not for inclusion into a production
> + build.
> +
> + For more information on KUnit and unit tests in general please refer
> + to the KUnit documentation in Documentation/dev-tools/kunit/.
> +
> + If unsure, say N.
thanks.
--
~Randy
next prev parent reply other threads:[~2020-04-15 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 8:28 [PATCH] Implement utf8 unit tests as a kunit test suite Ricardo Cañuelo
2020-04-15 16:19 ` Randy Dunlap [this message]
2020-04-15 18:40 ` Gabriel Krisman Bertazi
2020-04-16 7:51 ` Ricardo Cañuelo
2020-04-16 14:17 ` Gabriel Krisman Bertazi
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=31317125-42d6-3306-aa06-955eebb07623@infradead.org \
--to=rdunlap@infradead.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ricardo.canuelo@collabora.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;
as well as URLs for NNTP newsgroup(s).