[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b03a80a8-c887-7d85-4ca5-92446ee28054@kernel.org>
Date: Mon, 6 Jan 2020 11:54:39 -0700
From: shuah <shuah@...nel.org>
To: Alan Maguire <alan.maguire@...cle.com>, brendanhiggins@...gle.com,
linux-kselftest@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, kunit-dev@...glegroups.com,
keescook@...omium.org, yzaikin@...gle.com,
akpm@...ux-foundation.org, yamada.masahiro@...ionext.com,
catalin.marinas@....com, joe.lawrence@...hat.com,
penguin-kernel@...ove.sakura.ne.jp, urezki@...il.com,
andriy.shevchenko@...ux.intel.com, corbet@....net,
davidgow@...gle.com, adilger.kernel@...ger.ca, tytso@....edu,
mcgrof@...nel.org, linux-doc@...r.kernel.org,
shuah <shuah@...nel.org>
Subject: Re: [PATCH v6 linux-kselftest-test 0/6] kunit: support building
core/tests as modules
Hi Alan,
On 12/4/19 8:27 AM, Alan Maguire wrote:
> The current kunit execution model is to provide base kunit functionality
> and tests built-in to the kernel. The aim of this series is to allow
> building kunit itself and tests as modules. This in turn allows a
> simple form of selective execution; load the module you wish to test.
> In doing so, kunit itself (if also built as a module) will be loaded as
> an implicit dependency.
>
> Because this requires a core API modification - if a module delivers
> multiple suites, they must be declared with the kunit_test_suites()
> macro - we're proposing this patch set as a candidate to be applied to the
> test tree before too many kunit consumers appear. We attempt to deal
> with existing consumers in patch 3.
>
> Changes since v5:
> - fixed fs/ext4/Makefile to remove unneeded conditional compilation
> (Iurii, patch 3)
> - added Reviewed-by, Acked-by to patches 3, 4, 5 and 6
>
Are you planning to send v7 to address the kbuild issue? I can pull
them in for 5.6
thanks,
-- Shuah
Powered by blists - more mailing lists