From: Stephen Boyd <sboyd@kernel.org>
To: Brendan Higgins <brendanhiggins@google.com>,
frowand.list@gmail.com, gregkh@linuxfoundation.org,
jpoimboe@redhat.com, keescook@google.com,
kieran.bingham@ideasonboard.com, mcgrof@kernel.org,
peterz@infradead.org, robh@kernel.org, shuah@kernel.org,
tytso@mit.edu, yamada.masahiro@socionext.com
Cc: pmladek@suse.com, linux-doc@vger.kernel.org, amir73il@gmail.com,
dri-devel@lists.freedesktop.org, Alexander.Levin@microsoft.com,
linux-kselftest@vger.kernel.org, linux-nvdimm@lists.01.org,
khilman@baylibre.com, knut.omang@oracle.com, wfg@linux.intel.com,
joel@jms.id.au, rientjes@google.com, jdike@addtoit.com,
dan.carpenter@oracle.com, devicetree@vger.kernel.org,
linux-kbuild@vger.kernel.org, Tim.Bird@sony.com,
linux-um@lists.infradead.org, rostedt@goodmis.org,
julia.lawall@lip6.fr, kunit-dev@googlegroups.com, richard@nod.at,
rdunlap@infradead.org, linux-kernel@vger.kernel.org,
daniel@ffwll.ch, mpe@ellerman.id.au,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v9 01/18] kunit: test: add KUnit test runner core
Date: Mon, 15 Jul 2019 13:10:53 -0700 [thread overview]
Message-ID: <20190715201054.C69AA2086C@mail.kernel.org> (raw)
In-Reply-To: <20190712081744.87097-2-brendanhiggins@google.com>
Quoting Brendan Higgins (2019-07-12 01:17:27)
> Add core facilities for defining unit tests; this provides a common way
> to define test cases, functions that execute code which is under test
> and determine whether the code under test behaves as expected; this also
> provides a way to group together related test cases in test suites (here
> we call them test_modules).
>
> Just define test cases and how to execute them for now; setting
> expectations on code will be defined later.
>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
Minor nits below.
> diff --git a/kunit/test.c b/kunit/test.c
> new file mode 100644
> index 0000000000000..571e4c65deb5c
> --- /dev/null
> +++ b/kunit/test.c
> @@ -0,0 +1,189 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Base unit test (KUnit) API.
> + *
> + * Copyright (C) 2019, Google LLC.
> + * Author: Brendan Higgins <brendanhiggins@google.com>
> + */
> +
> +#include <linux/kernel.h>
> +#include <kunit/test.h>
> +
> +static void kunit_set_failure(struct kunit *test)
> +{
> + WRITE_ONCE(test->success, false);
> +}
> +
[...]
> +
> +void kunit_init_test(struct kunit *test, const char *name)
> +{
> + test->name = name;
> + test->success = true;
> +}
> +
> +/*
> + * Performs all logic to run a test case.
> + */
> +static void kunit_run_case(struct kunit_suite *suite,
> + struct kunit_case *test_case)
> +{
> + struct kunit test;
> + int ret = 0;
> +
> + kunit_init_test(&test, test_case->name);
> +
> + if (suite->init) {
> + ret = suite->init(&test);
Can you push the ret definition into this if scope? That way we can
avoid default initialize to 0 for it.
> + if (ret) {
> + kunit_err(&test, "failed to initialize: %d\n", ret);
> + kunit_set_failure(&test);
Do we need to 'test_case->success = test.success' here too? Or is the
test failure extracted somewhere else?
> + return;
> + }
> + }
> +
> + test_case->run_case(&test);
> +
> + if (suite->exit)
> + suite->exit(&test);
> +
> + test_case->success = test.success;
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Brendan Higgins <brendanhiggins@google.com>,
frowand.list@gmail.com, gregkh@linuxfoundation.org,
jpoimboe@redhat.com, keescook@google.com,
kieran.bingham@ideasonboard.com, mcgrof@kernel.org,
peterz@infradead.org, robh@kernel.org, shuah@kernel.org,
tytso@mit.edu, yamada.masahiro@socionext.com
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
kunit-dev@googlegroups.com, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-nvdimm@lists.01.org, linux-um@lists.infradead.org,
Alexander.Levin@microsoft.com, Tim.Bird@sony.com,
amir73il@gmail.com, dan.carpenter@oracle.com, daniel@ffwll.ch,
jdike@addtoit.com, joel@jms.id.au, julia.lawall@lip6.fr,
khilman@baylibre.com, knut.omang@oracle.com, logang@deltatee.com,
mpe@ellerman.id.au, pmladek@suse.com, rdunlap@infradead.org,
richard@nod.at, rientjes@google.com, rostedt@goodmis.org,
wfg@linux.intel.com, Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [PATCH v9 01/18] kunit: test: add KUnit test runner core
Date: Mon, 15 Jul 2019 13:10:53 -0700 [thread overview]
Message-ID: <20190715201054.C69AA2086C@mail.kernel.org> (raw)
In-Reply-To: <20190712081744.87097-2-brendanhiggins@google.com>
Quoting Brendan Higgins (2019-07-12 01:17:27)
> Add core facilities for defining unit tests; this provides a common way
> to define test cases, functions that execute code which is under test
> and determine whether the code under test behaves as expected; this also
> provides a way to group together related test cases in test suites (here
> we call them test_modules).
>
> Just define test cases and how to execute them for now; setting
> expectations on code will be defined later.
>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
Minor nits below.
> diff --git a/kunit/test.c b/kunit/test.c
> new file mode 100644
> index 0000000000000..571e4c65deb5c
> --- /dev/null
> +++ b/kunit/test.c
> @@ -0,0 +1,189 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Base unit test (KUnit) API.
> + *
> + * Copyright (C) 2019, Google LLC.
> + * Author: Brendan Higgins <brendanhiggins@google.com>
> + */
> +
> +#include <linux/kernel.h>
> +#include <kunit/test.h>
> +
> +static void kunit_set_failure(struct kunit *test)
> +{
> + WRITE_ONCE(test->success, false);
> +}
> +
[...]
> +
> +void kunit_init_test(struct kunit *test, const char *name)
> +{
> + test->name = name;
> + test->success = true;
> +}
> +
> +/*
> + * Performs all logic to run a test case.
> + */
> +static void kunit_run_case(struct kunit_suite *suite,
> + struct kunit_case *test_case)
> +{
> + struct kunit test;
> + int ret = 0;
> +
> + kunit_init_test(&test, test_case->name);
> +
> + if (suite->init) {
> + ret = suite->init(&test);
Can you push the ret definition into this if scope? That way we can
avoid default initialize to 0 for it.
> + if (ret) {
> + kunit_err(&test, "failed to initialize: %d\n", ret);
> + kunit_set_failure(&test);
Do we need to 'test_case->success = test.success' here too? Or is the
test failure extracted somewhere else?
> + return;
> + }
> + }
> +
> + test_case->run_case(&test);
> +
> + if (suite->exit)
> + suite->exit(&test);
> +
> + test_case->success = test.success;
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: frowand.list@gmail.com, gregkh@linuxfoundation.org,
jpoimboe@redhat.com, keescook@google.com,
kieran.bingham@ideasonboard.com, mcgrof@kernel.org,
peterz@infradead.org, robh@kernel.org, shuah@kernel.org,
tytso@mit.edu, yamada.masahiro@socionext.com
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
kunit-dev@googlegroups.com, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-nvdimm@lists.01.org, linux-um@lists.infradead.org,
Alexander.Levin@microsoft.com, Tim.Bird@sony.com,
amir73il@gmail.com, dan.carpenter@oracle.com, daniel@ffwll.ch,
jdike@addtoit.com, joel@jms.id.au, julia.lawall@lip6.fr,
khilman@baylibre.com, knut.omang@oracle.com, logang@deltatee.com,
mpe@ellerman.id.au, pmladek@suse.com, rdunlap@infradead.org,
richard@nod.at, rientjes@google.com, rostedt@goodmis.org,
wfg@linux.intel.com, Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [PATCH v9 01/18] kunit: test: add KUnit test runner core
Date: Mon, 15 Jul 2019 13:10:53 -0700 [thread overview]
Message-ID: <20190715201054.C69AA2086C@mail.kernel.org> (raw)
In-Reply-To: <20190712081744.87097-2-brendanhiggins@google.com>
Quoting Brendan Higgins (2019-07-12 01:17:27)
> Add core facilities for defining unit tests; this provides a common way
> to define test cases, functions that execute code which is under test
> and determine whether the code under test behaves as expected; this also
> provides a way to group together related test cases in test suites (here
> we call them test_modules).
>
> Just define test cases and how to execute them for now; setting
> expectations on code will be defined later.
>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
Minor nits below.
> diff --git a/kunit/test.c b/kunit/test.c
> new file mode 100644
> index 0000000000000..571e4c65deb5c
> --- /dev/null
> +++ b/kunit/test.c
> @@ -0,0 +1,189 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Base unit test (KUnit) API.
> + *
> + * Copyright (C) 2019, Google LLC.
> + * Author: Brendan Higgins <brendanhiggins@google.com>
> + */
> +
> +#include <linux/kernel.h>
> +#include <kunit/test.h>
> +
> +static void kunit_set_failure(struct kunit *test)
> +{
> + WRITE_ONCE(test->success, false);
> +}
> +
[...]
> +
> +void kunit_init_test(struct kunit *test, const char *name)
> +{
> + test->name = name;
> + test->success = true;
> +}
> +
> +/*
> + * Performs all logic to run a test case.
> + */
> +static void kunit_run_case(struct kunit_suite *suite,
> + struct kunit_case *test_case)
> +{
> + struct kunit test;
> + int ret = 0;
> +
> + kunit_init_test(&test, test_case->name);
> +
> + if (suite->init) {
> + ret = suite->init(&test);
Can you push the ret definition into this if scope? That way we can
avoid default initialize to 0 for it.
> + if (ret) {
> + kunit_err(&test, "failed to initialize: %d\n", ret);
> + kunit_set_failure(&test);
Do we need to 'test_case->success = test.success' here too? Or is the
test failure extracted somewhere else?
> + return;
> + }
> + }
> +
> + test_case->run_case(&test);
> +
> + if (suite->exit)
> + suite->exit(&test);
> +
> + test_case->success = test.success;
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Brendan Higgins <brendanhiggins@google.com>,
frowand.list@gmail.com, gregkh@linuxfoundation.org,
jpoimboe@redhat.com, keescook@google.com,
kieran.bingham@ideasonboard.com, mcgrof@kernel.org,
peterz@infradead.org, robh@kernel.org, shuah@kernel.org,
tytso@mit.edu, yamada.masahiro@socionext.com
Cc: devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
kunit-dev@googlegroups.com, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-nvdimm@lists.01.org, linux-um@lists.infradead.org,
Alexander.Levin@microsoft.com, Tim.Bird@sony.com,
amir73il@gmail.com, dan.carpenter@oracle.com, daniel@ffwll.ch,
jdike@addtoit.com, joel@jms.id.au, julia.lawall@lip6.fr,
khilman@baylibre.com, knut.omang@oracle.com, logang@deltatee.com,
mpe@ellerman.id.au, pmladek@suse.com, rdunlap@infradead.org,
richard@nod.at, rientjes@google.com, rostedt@goodmis.org,
wfg@linux.intel.com
Subject: Re: [PATCH v9 01/18] kunit: test: add KUnit test runner core
Date: Mon, 15 Jul 2019 13:10:53 -0700 [thread overview]
Message-ID: <20190715201054.C69AA2086C@mail.kernel.org> (raw)
In-Reply-To: <20190712081744.87097-2-brendanhiggins@google.com>
Quoting Brendan Higgins (2019-07-12 01:17:27)
> Add core facilities for defining unit tests; this provides a common way
> to define test cases, functions that execute code which is under test
> and determine whether the code under test behaves as expected; this also
> provides a way to group together related test cases in test suites (here
> we call them test_modules).
>
> Just define test cases and how to execute them for now; setting
> expectations on code will be defined later.
>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
Minor nits below.
> diff --git a/kunit/test.c b/kunit/test.c
> new file mode 100644
> index 0000000000000..571e4c65deb5c
> --- /dev/null
> +++ b/kunit/test.c
> @@ -0,0 +1,189 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Base unit test (KUnit) API.
> + *
> + * Copyright (C) 2019, Google LLC.
> + * Author: Brendan Higgins <brendanhiggins@google.com>
> + */
> +
> +#include <linux/kernel.h>
> +#include <kunit/test.h>
> +
> +static void kunit_set_failure(struct kunit *test)
> +{
> + WRITE_ONCE(test->success, false);
> +}
> +
[...]
> +
> +void kunit_init_test(struct kunit *test, const char *name)
> +{
> + test->name = name;
> + test->success = true;
> +}
> +
> +/*
> + * Performs all logic to run a test case.
> + */
> +static void kunit_run_case(struct kunit_suite *suite,
> + struct kunit_case *test_case)
> +{
> + struct kunit test;
> + int ret = 0;
> +
> + kunit_init_test(&test, test_case->name);
> +
> + if (suite->init) {
> + ret = suite->init(&test);
Can you push the ret definition into this if scope? That way we can
avoid default initialize to 0 for it.
> + if (ret) {
> + kunit_err(&test, "failed to initialize: %d\n", ret);
> + kunit_set_failure(&test);
Do we need to 'test_case->success = test.success' here too? Or is the
test failure extracted somewhere else?
> + return;
> + }
> + }
> +
> + test_case->run_case(&test);
> +
> + if (suite->exit)
> + suite->exit(&test);
> +
> + test_case->success = test.success;
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Boyd <sboyd@kernel.org>
To: Brendan Higgins <brendanhiggins@google.com>,
frowand.list@gmail.com, gregkh@linuxfoundation.org,
jpoimboe@redhat.com, keescook@google.com,
kieran.bingham@ideasonboard.com, mcgrof@kernel.org,
peterz@infradead.org, robh@kernel.org, shuah@kernel.org,
tytso@mit.edu, yamada.masahiro@socionext.com
Cc: pmladek@suse.com, linux-doc@vger.kernel.org, amir73il@gmail.com,
Brendan Higgins <brendanhiggins@google.com>,
dri-devel@lists.freedesktop.org, Alexander.Levin@microsoft.com,
linux-kselftest@vger.kernel.org, linux-nvdimm@lists.01.org,
khilman@baylibre.com, knut.omang@oracle.com, wfg@linux.intel.com,
joel@jms.id.au, rientjes@google.com, jdike@addtoit.com,
dan.carpenter@oracle.com, devicetree@vger.kernel.org,
linux-kbuild@vger.kernel.org, Tim.Bird@sony.com,
linux-um@lists.infradead.org, rostedt@goodmis.org,
julia.lawall@lip6.fr, kunit-dev@googlegroups.com, richard@nod.at,
rdunlap@infradead.org, linux-kernel@vger.kernel.org,
daniel@ffwll.ch, mpe@ellerman.id.au,
linux-fsdevel@vger.kernel.org, logang@deltatee.com
Subject: Re: [PATCH v9 01/18] kunit: test: add KUnit test runner core
Date: Mon, 15 Jul 2019 13:10:53 -0700 [thread overview]
Message-ID: <20190715201054.C69AA2086C@mail.kernel.org> (raw)
In-Reply-To: <20190712081744.87097-2-brendanhiggins@google.com>
Quoting Brendan Higgins (2019-07-12 01:17:27)
> Add core facilities for defining unit tests; this provides a common way
> to define test cases, functions that execute code which is under test
> and determine whether the code under test behaves as expected; this also
> provides a way to group together related test cases in test suites (here
> we call them test_modules).
>
> Just define test cases and how to execute them for now; setting
> expectations on code will be defined later.
>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
> Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Reviewed-by: Stephen Boyd <sboyd@kernel.org>
Minor nits below.
> diff --git a/kunit/test.c b/kunit/test.c
> new file mode 100644
> index 0000000000000..571e4c65deb5c
> --- /dev/null
> +++ b/kunit/test.c
> @@ -0,0 +1,189 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * Base unit test (KUnit) API.
> + *
> + * Copyright (C) 2019, Google LLC.
> + * Author: Brendan Higgins <brendanhiggins@google.com>
> + */
> +
> +#include <linux/kernel.h>
> +#include <kunit/test.h>
> +
> +static void kunit_set_failure(struct kunit *test)
> +{
> + WRITE_ONCE(test->success, false);
> +}
> +
[...]
> +
> +void kunit_init_test(struct kunit *test, const char *name)
> +{
> + test->name = name;
> + test->success = true;
> +}
> +
> +/*
> + * Performs all logic to run a test case.
> + */
> +static void kunit_run_case(struct kunit_suite *suite,
> + struct kunit_case *test_case)
> +{
> + struct kunit test;
> + int ret = 0;
> +
> + kunit_init_test(&test, test_case->name);
> +
> + if (suite->init) {
> + ret = suite->init(&test);
Can you push the ret definition into this if scope? That way we can
avoid default initialize to 0 for it.
> + if (ret) {
> + kunit_err(&test, "failed to initialize: %d\n", ret);
> + kunit_set_failure(&test);
Do we need to 'test_case->success = test.success' here too? Or is the
test failure extracted somewhere else?
> + return;
> + }
> + }
> +
> + test_case->run_case(&test);
> +
> + if (suite->exit)
> + suite->exit(&test);
> +
> + test_case->success = test.success;
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2019-07-15 20:13 UTC|newest]
Thread overview: 218+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 8:17 [PATCH v9 00/18] kunit: introduce KUnit, the Linux kernel unit testing framework Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 02/18] kunit: test: add test resource management API Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-15 20:24 ` Stephen Boyd
2019-07-15 20:24 ` Stephen Boyd
2019-07-15 20:24 ` Stephen Boyd
2019-07-15 20:24 ` Stephen Boyd
2019-07-15 20:24 ` Stephen Boyd
2019-07-15 20:30 ` Brendan Higgins
2019-07-15 20:30 ` Brendan Higgins
2019-07-15 20:30 ` Brendan Higgins
2019-07-15 20:30 ` Brendan Higgins
2019-07-15 20:51 ` Stephen Boyd
2019-07-15 20:51 ` Stephen Boyd
2019-07-15 20:51 ` Stephen Boyd
2019-07-15 20:51 ` Stephen Boyd
2019-07-15 20:51 ` Stephen Boyd
2019-07-12 8:17 ` [PATCH v9 03/18] kunit: test: add string_stream a std::stream like string builder Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-15 20:43 ` Stephen Boyd
2019-07-15 20:43 ` Stephen Boyd
2019-07-15 20:43 ` Stephen Boyd
2019-07-15 20:43 ` Stephen Boyd
2019-07-15 21:11 ` Brendan Higgins
2019-07-15 21:11 ` Brendan Higgins
2019-07-15 21:11 ` Brendan Higgins
2019-07-15 21:11 ` Brendan Higgins
2019-07-15 22:04 ` Stephen Boyd
2019-07-15 22:04 ` Stephen Boyd
2019-07-15 22:04 ` Stephen Boyd
2019-07-15 22:04 ` Stephen Boyd
2019-07-15 22:04 ` Stephen Boyd
2019-07-15 22:11 ` Brendan Higgins
2019-07-15 22:11 ` Brendan Higgins
2019-07-15 22:11 ` Brendan Higgins
2019-07-15 22:11 ` Brendan Higgins
2019-07-15 22:43 ` Brendan Higgins
2019-07-15 22:43 ` Brendan Higgins
2019-07-15 22:43 ` Brendan Higgins
2019-07-15 22:43 ` Brendan Higgins
2019-07-16 15:33 ` Stephen Boyd
2019-07-16 15:33 ` Stephen Boyd
2019-07-16 15:33 ` Stephen Boyd
2019-07-16 15:33 ` Stephen Boyd
2019-07-16 15:33 ` Stephen Boyd
2019-07-16 18:55 ` Brendan Higgins
2019-07-16 18:55 ` Brendan Higgins
2019-07-16 18:55 ` Brendan Higgins
2019-07-16 18:55 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 04/18] kunit: test: add kunit_stream a std::stream like logger Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-15 22:15 ` Stephen Boyd
2019-07-15 22:15 ` Stephen Boyd
2019-07-15 22:15 ` Stephen Boyd
2019-07-15 22:15 ` Stephen Boyd
2019-07-16 7:57 ` Brendan Higgins
2019-07-16 7:57 ` Brendan Higgins
2019-07-16 7:57 ` Brendan Higgins
2019-07-16 7:57 ` Brendan Higgins
2019-07-16 8:37 ` Brendan Higgins
2019-07-16 8:37 ` Brendan Higgins
2019-07-16 8:37 ` Brendan Higgins
2019-07-16 8:37 ` Brendan Higgins
2019-07-16 15:30 ` Stephen Boyd
2019-07-16 15:30 ` Stephen Boyd
2019-07-16 15:30 ` Stephen Boyd
2019-07-16 15:30 ` Stephen Boyd
2019-07-16 17:51 ` Brendan Higgins
2019-07-16 17:51 ` Brendan Higgins
2019-07-16 17:51 ` Brendan Higgins
2019-07-16 17:51 ` Brendan Higgins
2019-07-16 17:50 ` Stephen Boyd
2019-07-16 17:50 ` Stephen Boyd
2019-07-16 17:50 ` Stephen Boyd
2019-07-16 17:50 ` Stephen Boyd
2019-07-16 17:50 ` Stephen Boyd
2019-07-16 18:52 ` Brendan Higgins
2019-07-16 18:52 ` Brendan Higgins
2019-07-16 18:52 ` Brendan Higgins
2019-07-16 18:52 ` Brendan Higgins
2019-07-18 17:50 ` Stephen Boyd
2019-07-18 17:50 ` Stephen Boyd
2019-07-18 17:50 ` Stephen Boyd
2019-07-18 17:50 ` Stephen Boyd
2019-07-18 17:50 ` Stephen Boyd
[not found] ` <20190718175024.C3EC421019-+nuXSHJNwjE76Z2rM5mHXA@public.gmane.org>
2019-07-18 19:22 ` Brendan Higgins
2019-07-18 19:22 ` Brendan Higgins
2019-07-18 19:22 ` Brendan Higgins
2019-07-18 19:22 ` Brendan Higgins
2019-07-19 0:08 ` Brendan Higgins
2019-07-19 0:08 ` Brendan Higgins
2019-07-19 0:08 ` Brendan Higgins
2019-07-19 0:08 ` Brendan Higgins
2019-07-22 18:10 ` Brendan Higgins
2019-07-22 18:10 ` Brendan Higgins
2019-07-22 18:10 ` Brendan Higgins
2019-07-22 18:10 ` Brendan Higgins
2019-07-22 20:03 ` Stephen Boyd
2019-07-22 20:03 ` Stephen Boyd
2019-07-22 20:03 ` Stephen Boyd
2019-07-22 20:03 ` Stephen Boyd
2019-07-22 20:03 ` Stephen Boyd
[not found] ` <20190722200347.261D3218C9-+nuXSHJNwjE76Z2rM5mHXA@public.gmane.org>
2019-07-22 22:30 ` Brendan Higgins
2019-07-22 22:30 ` Brendan Higgins
2019-07-22 22:30 ` Brendan Higgins
2019-07-22 22:30 ` Brendan Higgins
2019-07-22 23:54 ` Stephen Boyd
2019-07-22 23:54 ` Stephen Boyd
2019-07-22 23:54 ` Stephen Boyd
2019-07-22 23:54 ` Stephen Boyd
2019-07-22 23:54 ` Stephen Boyd
[not found] ` <20190722235411.06C1320840-+nuXSHJNwjE76Z2rM5mHXA@public.gmane.org>
2019-07-23 0:32 ` Brendan Higgins
2019-07-23 0:32 ` Brendan Higgins
2019-07-23 0:32 ` Brendan Higgins
2019-07-23 0:32 ` Brendan Higgins
2019-07-24 7:31 ` Petr Mladek
2019-07-24 7:31 ` Petr Mladek
2019-07-24 7:31 ` Petr Mladek
2019-07-24 7:31 ` Petr Mladek
2019-07-25 20:21 ` Brendan Higgins
2019-07-25 20:21 ` Brendan Higgins
2019-07-25 20:21 ` Brendan Higgins
2019-07-25 20:21 ` Brendan Higgins
2019-07-26 8:31 ` Petr Mladek
2019-07-26 8:31 ` Petr Mladek
2019-07-26 8:31 ` Petr Mladek
2019-07-26 8:31 ` Petr Mladek
2019-08-01 18:55 ` Brendan Higgins
2019-08-01 18:55 ` Brendan Higgins
2019-08-01 18:55 ` Brendan Higgins
2019-08-01 18:55 ` Brendan Higgins
[not found] ` <CAFd5g46iAhDZ5C_chi7oYLVOkwcoj6+0nw+kPWuXhqWwWKd9jA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-01 18:59 ` Brendan Higgins
2019-08-01 18:59 ` Brendan Higgins
2019-08-01 18:59 ` Brendan Higgins
2019-08-01 18:59 ` Brendan Higgins
[not found] ` <CAFd5g473iFfvBnJs2pcwuJYgY+DpgD6RLzyDFL1otUuScgKUag-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-01 21:14 ` Stephen Boyd
2019-08-01 21:14 ` Stephen Boyd
2019-08-01 21:14 ` Stephen Boyd
2019-08-01 21:14 ` Stephen Boyd
2019-08-01 21:43 ` Brendan Higgins
2019-08-01 21:43 ` Brendan Higgins
2019-08-01 21:43 ` Brendan Higgins
2019-08-01 21:43 ` Brendan Higgins
2019-08-12 20:41 ` Brendan Higgins
2019-08-12 20:41 ` Brendan Higgins
2019-08-12 20:41 ` Brendan Higgins
2019-08-12 20:41 ` Brendan Higgins
2019-08-12 20:41 ` Brendan Higgins
2019-08-02 7:37 ` John Ogness
2019-08-02 7:37 ` John Ogness
2019-08-02 7:37 ` John Ogness
2019-08-02 7:37 ` John Ogness
2019-08-02 7:37 ` John Ogness
2019-08-12 21:12 ` Brendan Higgins
2019-08-12 21:12 ` Brendan Higgins
2019-08-12 21:12 ` Brendan Higgins
2019-08-12 21:12 ` Brendan Higgins
2019-08-12 21:12 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 08/18] objtool: add kunit_try_catch_throw to the noreturn list Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 10/18] kunit: test: add tests for kunit test abort Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 11/18] kunit: test: add the concept of assertions Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 12/18] kunit: test: add tests for KUnit managed resources Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
[not found] ` <20190712081744.87097-1-brendanhiggins-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2019-07-12 8:17 ` [PATCH v9 01/18] kunit: test: add KUnit test runner core Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-15 20:10 ` Stephen Boyd [this message]
2019-07-15 20:10 ` Stephen Boyd
2019-07-15 20:10 ` Stephen Boyd
2019-07-15 20:10 ` Stephen Boyd
2019-07-15 20:10 ` Stephen Boyd
2019-07-15 21:25 ` Brendan Higgins
2019-07-15 21:25 ` Brendan Higgins
2019-07-15 21:25 ` Brendan Higgins
2019-07-15 21:25 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 05/18] kunit: test: add the concept of expectations Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 06/18] kbuild: enable building KUnit Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
[not found] ` <20190712081744.87097-7-brendanhiggins-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2019-07-15 20:49 ` Stephen Boyd
2019-07-15 20:49 ` Stephen Boyd
2019-07-15 20:49 ` Stephen Boyd
2019-07-15 20:49 ` Stephen Boyd
2019-07-12 8:17 ` [PATCH v9 07/18] kunit: test: add initial tests Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 09/18] kunit: test: add support for test abort Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 13/18] kunit: tool: add Python wrappers for running KUnit tests Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 14/18] kunit: defconfig: add defconfigs for building " Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 17/18] kernel/sysctl-test: Add null pointer test for sysctl.c:proc_dointvec() Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 15/18] Documentation: kunit: add documentation for KUnit Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 16/18] MAINTAINERS: add entry for KUnit the unit testing framework Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` [PATCH v9 18/18] MAINTAINERS: add proc sysctl KUnit test to PROC SYSCTL section Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
2019-07-12 8:17 ` Brendan Higgins
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=20190715201054.C69AA2086C@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=Alexander.Levin@microsoft.com \
--cc=Tim.Bird@sony.com \
--cc=amir73il@gmail.com \
--cc=brendanhiggins@google.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jdike@addtoit.com \
--cc=joel@jms.id.au \
--cc=jpoimboe@redhat.com \
--cc=julia.lawall@lip6.fr \
--cc=keescook@google.com \
--cc=khilman@baylibre.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=knut.omang@oracle.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-um@lists.infradead.org \
--cc=mcgrof@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=rientjes@google.com \
--cc=robh@kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=tytso@mit.edu \
--cc=wfg@linux.intel.com \
--cc=yamada.masahiro@socionext.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.