Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: shuah@kernel.org, corbet@lwn.net
Cc: linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, dan.rue@linaro.org,
	anders.roxell@linaro.org, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] doc: kselftest: update for clarity on running kselftests in CI rings
Date: Mon, 26 Aug 2019 18:14:57 -0600	[thread overview]
Message-ID: <473cff26-9c01-fb72-12c5-e25535a3c129@linuxfoundation.org> (raw)
In-Reply-To: <20190827000753.25081-1-skhan@linuxfoundation.org>

On 8/26/19 6:07 PM, Shuah Khan wrote:
> Update to add clarity and recommendations on running newer kselftests
> on older kernels vs. matching the kernel and kselftest revisions.
> 
> The recommendation is "Match kernel revision and kselftest."
> 
> Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> ---
>   Documentation/dev-tools/kselftest.rst | 25 +++++++++++++++++++++++++
>   1 file changed, 25 insertions(+)
> 
> diff --git a/Documentation/dev-tools/kselftest.rst b/Documentation/dev-tools/kselftest.rst
> index 25604904fa6e..e55d9229fa8c 100644
> --- a/Documentation/dev-tools/kselftest.rst
> +++ b/Documentation/dev-tools/kselftest.rst
> @@ -12,6 +12,31 @@ write new tests using the framework on Kselftest wiki:
>   
>   https://kselftest.wiki.kernel.org/
>   
> +Recommendations on running kselftests in Continuous Integration test rings
> +=========================================================================

Sorry. I missed the "WARNING: Title underline too short."

Will send v2 with this corrected.

thanks,
-- Shuah

      reply	other threads:[~2019-08-27  0:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27  0:07 [PATCH] doc: kselftest: update for clarity on running kselftests in CI rings Shuah Khan
2019-08-27  0:14 ` Shuah Khan [this message]

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=473cff26-9c01-fb72-12c5-e25535a3c129@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=anders.roxell@linaro.org \
    --cc=corbet@lwn.net \
    --cc=dan.rue@linaro.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=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