All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Maguire <alan.maguire@oracle.com>
To: linux-kselftest@vger.kernel.org, brendanhiggins@google.com,
	skhan@linuxfoundation.org
Cc: mcgrof@kernel.org, keescook@chromium.org, yzaikin@google.com,
	akpm@linux-foundation.org, yamada.masahiro@socionext.com,
	catalin.marinas@arm.com, joe.lawrence@redhat.com,
	penguin-kernel@i-love.sakura.ne.jp, schowdary@nvidia.com,
	urezki@gmail.com, andriy.shevchenko@linux.intel.com,
	changbin.du@intel.com, kunit-dev@googlegroups.com,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Alan Maguire <alan.maguire@oracle.com>
Subject: [PATCH linux-kselftest-test 0/3] kunit: support module-based build
Date: Tue,  8 Oct 2019 15:43:49 +0100	[thread overview]
Message-ID: <1570545832-32326-1-git-send-email-alan.maguire@oracle.com> (raw)

For consumers wishing to run kunit on real hardware, it would be
ideal if the kunit framework and tests supported module-based builds.
This is an advantage as it reduces the test task to running
"modprobe mytests.ko", and CONFIG_KUNIT* options can be "always on"
(or rather "always m").  KUnit based tests will load the kunit module
as an implicit dependency.

Alan Maguire (3):
  kunit: allow kunit tests to be loaded as a module
  kunit: allow kunit to be loaded as a module
  kunit: update documentation to describe module-based build

 Documentation/dev-tools/kunit/faq.rst   |  3 ++-
 Documentation/dev-tools/kunit/index.rst |  3 +++
 Documentation/dev-tools/kunit/usage.rst | 16 +++++++++++++++
 include/kunit/test.h                    | 36 ++++++++++++++++++++++++---------
 kernel/sysctl-test.c                    |  6 +++++-
 kunit/Kconfig                           |  6 +++---
 kunit/Makefile                          |  9 +++++++++
 kunit/assert.c                          |  8 ++++++++
 kunit/example-test.c                    |  6 +++++-
 kunit/string-stream-test.c              |  9 +++++++--
 kunit/string-stream.c                   |  7 +++++++
 kunit/test-test.c                       |  8 ++++++--
 kunit/test.c                            | 12 +++++++++++
 kunit/try-catch.c                       |  8 ++++++--
 lib/Kconfig.debug                       |  4 ++--
 15 files changed, 117 insertions(+), 24 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2019-10-08 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 14:43 Alan Maguire [this message]
2019-10-08 14:43 ` [PATCH linux-kselftest-test 1/3] kunit: allow kunit tests to be loaded as a module Alan Maguire
2019-10-08 14:43 ` [PATCH linux-kselftest-test 2/3] kunit: allow kunit " Alan Maguire
2019-10-08 14:55   ` Andy Shevchenko
2019-10-08 15:15     ` Alan Maguire
2019-10-08 14:43 ` [PATCH linux-kselftest-test 3/3] kunit: update documentation to describe module-based build Alan Maguire

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=1570545832-32326-1-git-send-email-alan.maguire@oracle.com \
    --to=alan.maguire@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=brendanhiggins@google.com \
    --cc=catalin.marinas@arm.com \
    --cc=changbin.du@intel.com \
    --cc=joe.lawrence@redhat.com \
    --cc=keescook@chromium.org \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=schowdary@nvidia.com \
    --cc=skhan@linuxfoundation.org \
    --cc=urezki@gmail.com \
    --cc=yamada.masahiro@socionext.com \
    --cc=yzaikin@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.