All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masayoshi Mizuma <msys.mizuma@gmail.com>
To: Brendan Higgins <brendanhiggins@google.com>
Cc: corbet@lwn.net, frowand.list@gmail.com, keescook@google.com,
	kieran.bingham@ideasonboard.com, mcgrof@kernel.org,
	robh@kernel.org, shuah@kernel.org, yamada.masahiro@socionext.com,
	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,
	Felix Guo <felixguoxiuping@gmail.com>,
	wfg@linux.intel.com, joel@jms.id.au, 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,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 14/17] Documentation: kunit: add documentation for KUnit
Date: Wed, 24 Apr 2019 14:58:14 -0400	[thread overview]
Message-ID: <20190424185813.xabwr4lt6aunvpsd@gabell> (raw)
In-Reply-To: <20190404220652.19765-15-brendanhiggins@google.com>

Hi Brendan,

KUNIT_ASSERT_NOT_ERR_OR_NULL() should be replaced to
KUNIT_EXPECT_NOT_ERR_OR_NULL(), right?

On Thu, Apr 04, 2019 at 03:06:49PM -0700, Brendan Higgins wrote:
> Add documentation for KUnit, the Linux kernel unit testing framework.
> - Add intro and usage guide for KUnit
> - Add API reference
> 
> Signed-off-by: Felix Guo <felixguoxiuping@gmail.com>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> ---

<snip>

> diff --git a/Documentation/kunit/start.rst b/Documentation/kunit/start.rst
> new file mode 100644
> index 0000000000000..5cdba5091905e
> --- /dev/null
> +++ b/Documentation/kunit/start.rst

<snip>

> +Assertions
> +~~~~~~~~~~
> +
> +KUnit also has the concept of an *assertion*. An assertion is just like an
> +expectation except the assertion immediately terminates the test case if it is
> +not satisfied.
> +
> +For example:
> +
> +.. code-block:: c
> +
> +	static void mock_test_do_expect_default_return(struct kunit *test)
> +	{
> +		struct mock_test_context *ctx = test->priv;
> +		struct mock *mock = ctx->mock;
> +		int param0 = 5, param1 = -5;
> +		const char *two_param_types[] = {"int", "int"};
> +		const void *two_params[] = {&param0, &param1};
> +		const void *ret;
> +
> +		ret = mock->do_expect(mock,
> +				      "test_printk", test_printk,
> +				      two_param_types, two_params,
> +				      ARRAY_SIZE(two_params));

> +		KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ret);

		KUNIT_EXPECT_NOT_ERR_OR_NULL(test, ret);

> +		KUNIT_EXPECT_EQ(test, -4, *((int *) ret));
> +	}
> +
> +In this example, the method under test should return a pointer to a value, so
> +if the pointer returned by the method is null or an errno, we don't want to
> +bother continuing the test since the following expectation could crash the test

> +case. `ASSERT_NOT_ERR_OR_NULL(...)` allows us to bail out of the test case if

  +case. `KUNIT_EXPECT_NOT_ERR_OR_NULL(...)` allows us to bail out of the test case if

Thanks!
Masa

WARNING: multiple messages have this Message-ID (diff)
From: Masayoshi Mizuma <msys.mizuma@gmail.com>
To: Brendan Higgins <brendanhiggins@google.com>
Cc: corbet@lwn.net, frowand.list@gmail.com, keescook@google.com,
	kieran.bingham@ideasonboard.com, mcgrof@kernel.org,
	robh@kernel.org, shuah@kernel.org, yamada.masahiro@socionext.com,
	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,
	Felix Guo <felixguoxiuping@gmail.com>,
	wfg@linux.intel.com, joel@jms.id.au, 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,
	gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
	daniel@ffwll.ch, mpe@ellerman.id.au,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v1 14/17] Documentation: kunit: add documentation for KUnit
Date: Wed, 24 Apr 2019 14:58:14 -0400	[thread overview]
Message-ID: <20190424185813.xabwr4lt6aunvpsd@gabell> (raw)
In-Reply-To: <20190404220652.19765-15-brendanhiggins@google.com>

Hi Brendan,

KUNIT_ASSERT_NOT_ERR_OR_NULL() should be replaced to
KUNIT_EXPECT_NOT_ERR_OR_NULL(), right?

On Thu, Apr 04, 2019 at 03:06:49PM -0700, Brendan Higgins wrote:
> Add documentation for KUnit, the Linux kernel unit testing framework.
> - Add intro and usage guide for KUnit
> - Add API reference
> 
> Signed-off-by: Felix Guo <felixguoxiuping@gmail.com>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> ---

<snip>

> diff --git a/Documentation/kunit/start.rst b/Documentation/kunit/start.rst
> new file mode 100644
> index 0000000000000..5cdba5091905e
> --- /dev/null
> +++ b/Documentation/kunit/start.rst

<snip>

> +Assertions
> +~~~~~~~~~~
> +
> +KUnit also has the concept of an *assertion*. An assertion is just like an
> +expectation except the assertion immediately terminates the test case if it is
> +not satisfied.
> +
> +For example:
> +
> +.. code-block:: c
> +
> +	static void mock_test_do_expect_default_return(struct kunit *test)
> +	{
> +		struct mock_test_context *ctx = test->priv;
> +		struct mock *mock = ctx->mock;
> +		int param0 = 5, param1 = -5;
> +		const char *two_param_types[] = {"int", "int"};
> +		const void *two_params[] = {&param0, &param1};
> +		const void *ret;
> +
> +		ret = mock->do_expect(mock,
> +				      "test_printk", test_printk,
> +				      two_param_types, two_params,
> +				      ARRAY_SIZE(two_params));

> +		KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ret);

		KUNIT_EXPECT_NOT_ERR_OR_NULL(test, ret);

> +		KUNIT_EXPECT_EQ(test, -4, *((int *) ret));
> +	}
> +
> +In this example, the method under test should return a pointer to a value, so
> +if the pointer returned by the method is null or an errno, we don't want to
> +bother continuing the test since the following expectation could crash the test

> +case. `ASSERT_NOT_ERR_OR_NULL(...)` allows us to bail out of the test case if

  +case. `KUNIT_EXPECT_NOT_ERR_OR_NULL(...)` allows us to bail out of the test case if

Thanks!
Masa

WARNING: multiple messages have this Message-ID (diff)
From: msys.mizuma at gmail.com (Masayoshi Mizuma)
Subject: [PATCH v1 14/17] Documentation: kunit: add documentation for KUnit
Date: Wed, 24 Apr 2019 14:58:14 -0400	[thread overview]
Message-ID: <20190424185813.xabwr4lt6aunvpsd@gabell> (raw)
In-Reply-To: <20190404220652.19765-15-brendanhiggins@google.com>

Hi Brendan,

KUNIT_ASSERT_NOT_ERR_OR_NULL() should be replaced to
KUNIT_EXPECT_NOT_ERR_OR_NULL(), right?

On Thu, Apr 04, 2019 at 03:06:49PM -0700, Brendan Higgins wrote:
> Add documentation for KUnit, the Linux kernel unit testing framework.
> - Add intro and usage guide for KUnit
> - Add API reference
> 
> Signed-off-by: Felix Guo <felixguoxiuping at gmail.com>
> Signed-off-by: Brendan Higgins <brendanhiggins at google.com>
> ---

<snip>

> diff --git a/Documentation/kunit/start.rst b/Documentation/kunit/start.rst
> new file mode 100644
> index 0000000000000..5cdba5091905e
> --- /dev/null
> +++ b/Documentation/kunit/start.rst

<snip>

> +Assertions
> +~~~~~~~~~~
> +
> +KUnit also has the concept of an *assertion*. An assertion is just like an
> +expectation except the assertion immediately terminates the test case if it is
> +not satisfied.
> +
> +For example:
> +
> +.. code-block:: c
> +
> +	static void mock_test_do_expect_default_return(struct kunit *test)
> +	{
> +		struct mock_test_context *ctx = test->priv;
> +		struct mock *mock = ctx->mock;
> +		int param0 = 5, param1 = -5;
> +		const char *two_param_types[] = {"int", "int"};
> +		const void *two_params[] = {&param0, &param1};
> +		const void *ret;
> +
> +		ret = mock->do_expect(mock,
> +				      "test_printk", test_printk,
> +				      two_param_types, two_params,
> +				      ARRAY_SIZE(two_params));

> +		KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ret);

		KUNIT_EXPECT_NOT_ERR_OR_NULL(test, ret);

> +		KUNIT_EXPECT_EQ(test, -4, *((int *) ret));
> +	}
> +
> +In this example, the method under test should return a pointer to a value, so
> +if the pointer returned by the method is null or an errno, we don't want to
> +bother continuing the test since the following expectation could crash the test

> +case. `ASSERT_NOT_ERR_OR_NULL(...)` allows us to bail out of the test case if

  +case. `KUNIT_EXPECT_NOT_ERR_OR_NULL(...)` allows us to bail out of the test case if

Thanks!
Masa

WARNING: multiple messages have this Message-ID (diff)
From: msys.mizuma@gmail.com (Masayoshi Mizuma)
Subject: [PATCH v1 14/17] Documentation: kunit: add documentation for KUnit
Date: Wed, 24 Apr 2019 14:58:14 -0400	[thread overview]
Message-ID: <20190424185813.xabwr4lt6aunvpsd@gabell> (raw)
Message-ID: <20190424185814.R_Mjyy8n4R1AQpTRK1u6hs3wnVFueC2V_WMl_H0eZdw@z> (raw)
In-Reply-To: <20190404220652.19765-15-brendanhiggins@google.com>

Hi Brendan,

KUNIT_ASSERT_NOT_ERR_OR_NULL() should be replaced to
KUNIT_EXPECT_NOT_ERR_OR_NULL(), right?

On Thu, Apr 04, 2019@03:06:49PM -0700, Brendan Higgins wrote:
> Add documentation for KUnit, the Linux kernel unit testing framework.
> - Add intro and usage guide for KUnit
> - Add API reference
> 
> Signed-off-by: Felix Guo <felixguoxiuping at gmail.com>
> Signed-off-by: Brendan Higgins <brendanhiggins at google.com>
> ---

<snip>

> diff --git a/Documentation/kunit/start.rst b/Documentation/kunit/start.rst
> new file mode 100644
> index 0000000000000..5cdba5091905e
> --- /dev/null
> +++ b/Documentation/kunit/start.rst

<snip>

> +Assertions
> +~~~~~~~~~~
> +
> +KUnit also has the concept of an *assertion*. An assertion is just like an
> +expectation except the assertion immediately terminates the test case if it is
> +not satisfied.
> +
> +For example:
> +
> +.. code-block:: c
> +
> +	static void mock_test_do_expect_default_return(struct kunit *test)
> +	{
> +		struct mock_test_context *ctx = test->priv;
> +		struct mock *mock = ctx->mock;
> +		int param0 = 5, param1 = -5;
> +		const char *two_param_types[] = {"int", "int"};
> +		const void *two_params[] = {&param0, &param1};
> +		const void *ret;
> +
> +		ret = mock->do_expect(mock,
> +				      "test_printk", test_printk,
> +				      two_param_types, two_params,
> +				      ARRAY_SIZE(two_params));

> +		KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ret);

		KUNIT_EXPECT_NOT_ERR_OR_NULL(test, ret);

> +		KUNIT_EXPECT_EQ(test, -4, *((int *) ret));
> +	}
> +
> +In this example, the method under test should return a pointer to a value, so
> +if the pointer returned by the method is null or an errno, we don't want to
> +bother continuing the test since the following expectation could crash the test

> +case. `ASSERT_NOT_ERR_OR_NULL(...)` allows us to bail out of the test case if

  +case. `KUNIT_EXPECT_NOT_ERR_OR_NULL(...)` allows us to bail out of the test case if

Thanks!
Masa

WARNING: multiple messages have this Message-ID (diff)
From: Masayoshi Mizuma <msys.mizuma@gmail.com>
To: Brendan Higgins <brendanhiggins@google.com>
Cc: linux-doc@vger.kernel.org, amir73il@gmail.com,
	dri-devel@lists.freedesktop.org, Alexander.Levin@microsoft.com,
	yamada.masahiro@socionext.com, devicetree@vger.kernel.org,
	mpe@ellerman.id.au, linux-kselftest@vger.kernel.org,
	shuah@kernel.org, robh@kernel.org, frowand.list@gmail.com,
	corbet@lwn.net, khilman@baylibre.com, knut.omang@oracle.com,
	kieran.bingham@ideasonboard.com,
	Felix Guo <felixguoxiuping@gmail.com>,
	wfg@linux.intel.com, joel@jms.id.au, Tim.Bird@sony.com,
	dan.carpenter@oracle.com, pmladek@suse.com,
	linux-kbuild@vger.kernel.org, jdike@addtoit.com,
	linux-um@lists.infradead.org, rostedt@goodmis.org,
	julia.lawall@lip6.fr, kunit-dev@googlegroups.com, richard@nod.at,
	gregkh@linuxfoundation.org, linux-nvdimm@lists.01.org,
	linux-kernel@vger.kernel.org, mcgrof@kernel.org, daniel@ffwll.ch,
	keescook@google.com, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v1 14/17] Documentation: kunit: add documentation for KUnit
Date: Wed, 24 Apr 2019 14:58:14 -0400	[thread overview]
Message-ID: <20190424185813.xabwr4lt6aunvpsd@gabell> (raw)
In-Reply-To: <20190404220652.19765-15-brendanhiggins@google.com>

Hi Brendan,

KUNIT_ASSERT_NOT_ERR_OR_NULL() should be replaced to
KUNIT_EXPECT_NOT_ERR_OR_NULL(), right?

On Thu, Apr 04, 2019 at 03:06:49PM -0700, Brendan Higgins wrote:
> Add documentation for KUnit, the Linux kernel unit testing framework.
> - Add intro and usage guide for KUnit
> - Add API reference
> 
> Signed-off-by: Felix Guo <felixguoxiuping@gmail.com>
> Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
> ---

<snip>

> diff --git a/Documentation/kunit/start.rst b/Documentation/kunit/start.rst
> new file mode 100644
> index 0000000000000..5cdba5091905e
> --- /dev/null
> +++ b/Documentation/kunit/start.rst

<snip>

> +Assertions
> +~~~~~~~~~~
> +
> +KUnit also has the concept of an *assertion*. An assertion is just like an
> +expectation except the assertion immediately terminates the test case if it is
> +not satisfied.
> +
> +For example:
> +
> +.. code-block:: c
> +
> +	static void mock_test_do_expect_default_return(struct kunit *test)
> +	{
> +		struct mock_test_context *ctx = test->priv;
> +		struct mock *mock = ctx->mock;
> +		int param0 = 5, param1 = -5;
> +		const char *two_param_types[] = {"int", "int"};
> +		const void *two_params[] = {&param0, &param1};
> +		const void *ret;
> +
> +		ret = mock->do_expect(mock,
> +				      "test_printk", test_printk,
> +				      two_param_types, two_params,
> +				      ARRAY_SIZE(two_params));

> +		KUNIT_ASSERT_NOT_ERR_OR_NULL(test, ret);

		KUNIT_EXPECT_NOT_ERR_OR_NULL(test, ret);

> +		KUNIT_EXPECT_EQ(test, -4, *((int *) ret));
> +	}
> +
> +In this example, the method under test should return a pointer to a value, so
> +if the pointer returned by the method is null or an errno, we don't want to
> +bother continuing the test since the following expectation could crash the test

> +case. `ASSERT_NOT_ERR_OR_NULL(...)` allows us to bail out of the test case if

  +case. `KUNIT_EXPECT_NOT_ERR_OR_NULL(...)` allows us to bail out of the test case if

Thanks!
Masa

_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  reply	other threads:[~2019-04-24 18:58 UTC|newest]

Thread overview: 107+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 22:06 [PATCH v1 00/17] kunit: introduce KUnit, the Linux kernel unit testing framework Brendan Higgins
2019-04-04 22:06 ` Brendan Higgins
2019-04-04 22:06 ` Brendan Higgins
2019-04-04 22:06 ` brendanhiggins
2019-04-04 22:06 ` [PATCH v1 01/17] kunit: test: add KUnit test runner core Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` brendanhiggins
     [not found] ` <20190404220652.19765-1-brendanhiggins-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2019-04-04 22:06   ` [PATCH v1 02/17] kunit: test: add test resource management API Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` brendanhiggins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06   ` [PATCH v1 03/17] kunit: test: add string_stream a std::stream like string builder Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` brendanhiggins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06   ` [PATCH v1 05/17] kunit: test: add the concept of expectations Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` brendanhiggins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06   ` [PATCH v1 06/17] kbuild: enable building KUnit Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` brendanhiggins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06   ` [PATCH v1 07/17] kunit: test: add initial tests Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` brendanhiggins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06   ` [PATCH v1 10/17] kunit: test: add the concept of assertions Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` brendanhiggins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06   ` [PATCH v1 12/17] kunit: tool: add Python wrappers for running KUnit tests Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` brendanhiggins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06   ` [PATCH v1 15/17] MAINTAINERS: add entry for KUnit the unit testing framework Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` brendanhiggins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06   ` [PATCH v1 16/17] kernel/sysctl-test: Add null pointer test for sysctl.c:proc_dointvec() Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06     ` brendanhiggins
2019-04-04 22:06     ` Brendan Higgins
2019-04-04 22:06 ` [PATCH v1 04/17] kunit: test: add kunit_stream a std::stream like logger Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` brendanhiggins
2019-04-04 22:06 ` [PATCH v1 08/17] kunit: test: add support for test abort Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` brendanhiggins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06 ` [PATCH v1 09/17] kunit: test: add tests for kunit " Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` brendanhiggins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06 ` [PATCH v1 11/17] kunit: test: add test managed resource tests Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` brendanhiggins
2019-04-04 22:06   ` Brendan Higgins
2019-04-24 19:00   ` Masayoshi Mizuma
2019-04-24 19:00     ` Masayoshi Mizuma
2019-04-24 19:00     ` Masayoshi Mizuma
2019-04-24 19:00     ` msys.mizuma
2019-04-24 19:00     ` Masayoshi Mizuma
2019-04-25 21:39     ` Brendan Higgins
2019-04-25 21:39       ` Brendan Higgins
2019-04-25 21:39       ` Brendan Higgins
2019-04-25 21:39       ` brendanhiggins
2019-04-25 21:39       ` Brendan Higgins
2019-04-04 22:06 ` [PATCH v1 13/17] kunit: defconfig: add defconfigs for building KUnit tests Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` brendanhiggins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06 ` [PATCH v1 14/17] Documentation: kunit: add documentation for KUnit Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` brendanhiggins
2019-04-04 22:06   ` Brendan Higgins
2019-04-24 18:58   ` Masayoshi Mizuma [this message]
2019-04-24 18:58     ` Masayoshi Mizuma
2019-04-24 18:58     ` Masayoshi Mizuma
2019-04-24 18:58     ` msys.mizuma
2019-04-24 18:58     ` Masayoshi Mizuma
2019-04-25 21:37     ` Brendan Higgins
2019-04-25 21:37       ` Brendan Higgins
2019-04-25 21:37       ` Brendan Higgins
2019-04-25 21:37       ` brendanhiggins
2019-04-25 21:37       ` Brendan Higgins
2019-04-04 22:06 ` [PATCH v1 17/17] MAINTAINERS: add proc sysctl KUnit test to PROC SYSCTL section Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` Brendan Higgins
2019-04-04 22:06   ` brendanhiggins
2019-04-04 22:06   ` 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=20190424185813.xabwr4lt6aunvpsd@gabell \
    --to=msys.mizuma@gmail.com \
    --cc=Alexander.Levin@microsoft.com \
    --cc=Tim.Bird@sony.com \
    --cc=amir73il@gmail.com \
    --cc=brendanhiggins@google.com \
    --cc=corbet@lwn.net \
    --cc=dan.carpenter@oracle.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=felixguoxiuping@gmail.com \
    --cc=frowand.list@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jdike@addtoit.com \
    --cc=joel@jms.id.au \
    --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-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=pmladek@suse.com \
    --cc=richard@nod.at \
    --cc=robh@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=shuah@kernel.org \
    --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.