linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: shuah@kernel.org (Shuah Khan)
Subject: [PATCH v2] doc: dev-tools: kselftest.rst: update contributing new tests
Date: Tue, 24 Apr 2018 13:35:47 -0600	[thread overview]
Message-ID: <d65f770f-e871-53e4-828f-4ba94df90ae3@kernel.org> (raw)
Message-ID: <20180424193547.Xz-dunacfL-5xyA8otylM3Ra3TKk1RGGWft97WL79cM@z> (raw)
In-Reply-To: <20180419102825.2990-1-anders.roxell@linaro.org>

On 04/19/2018 04:28 AM, Anders Roxell wrote:
> Add a description that the kernel headers should be used as far as it is
> possible and then the system headers.
> 
> Signed-off-by: Anders Roxell <anders.roxell at linaro.org>
> ---
>  Documentation/dev-tools/kselftest.rst | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/dev-tools/kselftest.rst b/Documentation/dev-tools/kselftest.rst
> index e80850eefe13..3bf371a938d0 100644
> --- a/Documentation/dev-tools/kselftest.rst
> +++ b/Documentation/dev-tools/kselftest.rst
> @@ -151,6 +151,11 @@ Contributing new tests (details)
>     TEST_FILES, TEST_GEN_FILES mean it is the file which is used by
>     test.
>  
> + * First use the headers inside the kernel source and/or git repo, and then the
> +   system headers.  Headers for the kernel release as opposed to headers
> +   installed by the distro on the system should be the primary focus to be able
> +   to find regressions.
> +
>  Test Harness
>  ============
>  
> 

Here is my reviewed by for this to go through documentation tree.

Reviewed-by: Shuah Khan (Samsung OSG) <shuah at kernel.org>

thanks,
-- Shuah

--
To unsubscribe from this list: send the line "unsubscribe linux-kselftest" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2018-04-24 19:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-17  8:46 [PATCH] doc: dev-tools: kselftest.rst: update contributing new tests anders.roxell
2018-04-17  8:46 ` Anders Roxell
2018-04-18 14:48 ` shuah
2018-04-18 14:48   ` Shuah Khan
2018-04-19 10:28 ` [PATCH v2] " anders.roxell
2018-04-19 10:28   ` Anders Roxell
2018-04-24 19:35   ` shuah [this message]
2018-04-24 19:35     ` Shuah Khan
2018-04-27 22:56   ` corbet
2018-04-27 22:56     ` Jonathan Corbet
2018-06-29 10:02 [PATCH] " anders.roxell
2018-06-29 12:52 ` [PATCH v2] " anders.roxell
2018-06-29 12:52   ` Anders Roxell
2018-06-29 13:29   ` shuah
2018-06-29 13:29     ` Shuah Khan
2018-06-29 15:02   ` corbet
2018-06-29 15:02     ` Jonathan Corbet

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=d65f770f-e871-53e4-828f-4ba94df90ae3@kernel.org \
    --to=shuah@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).