lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 26 Jun 2020 14:09:17 -0700 From: Brendan Higgins <brendanhiggins@...gle.com> To: jdike@...toit.com, richard@....at, anton.ivanov@...bridgegreys.com, arnd@...db.de, keescook@...omium.org, skhan@...uxfoundation.org, alan.maguire@...cle.com, yzaikin@...gle.com, davidgow@...gle.com, akpm@...ux-foundation.org, rppt@...ux.ibm.com, frowand.list@...il.com, catalin.marinas@....com, will@...nel.org, monstr@...str.eu, mpe@...erman.id.au, benh@...nel.crashing.org, paulus@...ba.org, chris@...kel.net, jcmvbkbc@...il.com Cc: gregkh@...uxfoundation.org, sboyd@...nel.org, logang@...tatee.com, mcgrof@...nel.org, linux-um@...ts.infradead.org, linux-arch@...r.kernel.org, linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com, linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linuxppc-dev@...ts.ozlabs.org, linux-xtensa@...ux-xtensa.org, Brendan Higgins <brendanhiggins@...gle.com> Subject: [PATCH v5 12/12] Documentation: kunit: add a brief blurb about kunit_test_suite Add a brief blurb saying how and when the kunit_test_suite() macro works to the usage documentation. Signed-off-by: Brendan Higgins <brendanhiggins@...gle.com> --- Documentation/dev-tools/kunit/usage.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/Documentation/dev-tools/kunit/usage.rst b/Documentation/dev-tools/kunit/usage.rst index 3c3fe8b5feccf..961d3ea3ca19a 100644 --- a/Documentation/dev-tools/kunit/usage.rst +++ b/Documentation/dev-tools/kunit/usage.rst @@ -211,6 +211,11 @@ KUnit test framework. .. note:: A test case will only be run if it is associated with a test suite. +``kunit_test_suite(...)`` is a macro which tells the linker to put the specified +test suite in a special linker section so that it can be run by KUnit either +after late_init, or when the test module is loaded (depending on whether the +test was built in or not). + For more information on these types of things see the :doc:`api/test`. Isolating Behavior -- 2.27.0.212.ge8ba1cc988-goog
Powered by blists - more mailing lists