Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Liam Beguin <liambeguin@gmail.com>
Cc: geert@linux-m68k.org, peda@axentia.se, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 5/5] iio: test: rework Kconfig to support modules
Date: Sat, 16 Jul 2022 19:03:31 +0100	[thread overview]
Message-ID: <20220716190331.43f5bc03@jic23-huawei> (raw)
In-Reply-To: <20220710013109.3349104-6-liambeguin@gmail.com>

On Sat,  9 Jul 2022 21:31:09 -0400
Liam Beguin <liambeguin@gmail.com> wrote:

> Rework the IIO test Kconfig to support building KUnit tests as modules.
> This lets users execute tests at runtime in addition to the usual
> tools/testing/kunit/kunit.py script.
> 
> Signed-off-by: Liam Beguin <liambeguin@gmail.com>
One trivial comment inline.  Fixed that up and applied to the togreg branch
of iio.git. Not I'll only push out as testing for now as will be rebasing
the tree after rc1.

Jonathan


> ---
>  drivers/iio/test/Kconfig | 24 +++++++++++++++++-------
>  1 file changed, 17 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/iio/test/Kconfig b/drivers/iio/test/Kconfig
> index 7dbf51bc4934..82924727b2cc 100644
> --- a/drivers/iio/test/Kconfig
> +++ b/drivers/iio/test/Kconfig
> @@ -5,15 +5,25 @@
>  
>  # Keep in alphabetical order
>  config IIO_RESCALE_KUNIT_TEST
> -	bool "Test IIO rescale conversion functions"
> -	depends on KUNIT=y && IIO_RESCALE=y
> +	tristate "Test IIO rescale conversion functions" if !KUNIT_ALL_TESTS
> +	depends on KUNIT && IIO_RESCALE
>  	default KUNIT_ALL_TESTS
>  	help
> -	  If you want to run tests on the iio-rescale code say Y here.
> +	  build unit tests for the iio-rescale code.

Build

>  
> -	  This takes advantage of ARCH=um to run tests and should be used by
> -	  developers to tests their changes to the rescaling logic.
> +	  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.
>  
>  config IIO_FORMAT_KUNIT_TEST
> -        bool "Test IIO formatting functions"
> -        depends on KUNIT=y
> +	tristate "Test IIO formatting functions" if !KUNIT_ALL_TESTS
> +	depends on KUNIT
> +	default KUNIT_ALL_TESTS
> +	help
> +	  build unit tests for the IIO formatting functions.
> +
> +	  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.


      reply	other threads:[~2022-07-16 17:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-10  1:31 [PATCH v1 0/5] Add module build support for KUnit IIO tests Liam Beguin
2022-07-10  1:31 ` [PATCH v1 1/5] iio: test: rescale: add MODULE_* information Liam Beguin
2022-07-10  1:31 ` [PATCH v1 2/5] iio: test: format: " Liam Beguin
2022-07-10  1:31 ` [PATCH v1 3/5] iio: test: format: follow CONFIG_ naming convention Liam Beguin
2022-07-10  1:31 ` [PATCH v1 4/5] iio: afe: rescale: export symbols used during testing Liam Beguin
2022-07-10  1:31 ` [PATCH v1 5/5] iio: test: rework Kconfig to support modules Liam Beguin
2022-07-16 18:03   ` Jonathan Cameron [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=20220716190331.43f5bc03@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=liambeguin@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peda@axentia.se \
    /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