From: Anders Roxell <anders.roxell@linaro.org>
To: shuah@kernel.org, corbet@lwn.net
Cc: linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Anders Roxell <anders.roxell@linaro.org>
Subject: [PATCH v2] doc: dev-tools: kselftest.rst: update contributing new tests
Date: Thu, 19 Apr 2018 12:28:25 +0200 [thread overview]
Message-ID: <20180419102825.2990-1-anders.roxell@linaro.org> (raw)
In-Reply-To: <20180417084631.11242-1-anders.roxell@linaro.org>
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@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
============
--
2.11.0
next prev parent reply other threads:[~2018-04-19 10:28 UTC|newest]
Thread overview: 8+ 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-18 14:48 ` Shuah Khan
2018-04-19 10:28 ` Anders Roxell [this message]
2018-04-24 19:35 ` [PATCH v2] " Shuah Khan
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 13:29 ` Shuah Khan
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=20180419102825.2990-1-anders.roxell@linaro.org \
--to=anders.roxell@linaro.org \
--cc=corbet@lwn.net \
--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;
as well as URLs for NNTP newsgroup(s).