[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABVgOS=F9K_AzoWjKPRT9m014NAo37vKHYEp-jHWDt5M+pkzSw@mail.gmail.com>
Date: Sat, 2 Oct 2021 11:10:40 +0800
From: David Gow <davidgow@...gle.com>
To: Jeremy Kerr <jk@...econstruct.com.au>
Cc: Networking <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Matt Johnston <matt@...econstruct.com.au>,
Brendan Higgins <brendanhiggins@...gle.com>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@...r.kernel.org>
Subject: Re: [PATCH net-next 1/2] mctp: test: disallow MCTP_TEST when building
as a module
On Sat, Oct 2, 2021 at 10:27 AM Jeremy Kerr <jk@...econstruct.com.au> wrote:
>
> The current kunit infrastructure defines its own module_init() when
> built as a module, which conflicts with the mctp core's own.
>
> So, only allow MCTP_TEST when both MCTP and KUNIT are built-in.
>
> Reported-by: kernel test robot <lkp@...el.com>
> Signed-off-by: Jeremy Kerr <jk@...econstruct.com.au>
> ---
This looks good to me. I don't think you'll be the only person to hit
this issue, so -- while it's probably overall nicer if tests can sit
in their own module -- we'll look into finding a way of supporting
this with KUnit at some point. In the meantime, though, this is a
reasonable workaround.
Reviewed-by: David Gow <davidgow@...gle.com>
-- David
> net/mctp/Kconfig | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/mctp/Kconfig b/net/mctp/Kconfig
> index 15267a5043d9..868c92272cbd 100644
> --- a/net/mctp/Kconfig
> +++ b/net/mctp/Kconfig
> @@ -13,6 +13,6 @@ menuconfig MCTP
> channel.
>
> config MCTP_TEST
> - tristate "MCTP core tests" if !KUNIT_ALL_TESTS
> - depends on MCTP && KUNIT
> + bool "MCTP core tests" if !KUNIT_ALL_TESTS
> + depends on MCTP=y && KUNIT=y
> default KUNIT_ALL_TESTS
> --
> 2.30.2
>
Powered by blists - more mailing lists