All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Palethorpe via ltp <ltp@lists.linux.it>
To: ltp@lists.linux.it
Cc: Richard Palethorpe <rpalethorpe@suse.com>
Subject: [LTP] [PATCH] Create policy for testing unstable kernel features
Date: Thu,  3 Feb 2022 10:18:03 +0000	[thread overview]
Message-ID: <20220203101803.10204-1-rpalethorpe@suse.com> (raw)
In-Reply-To: <YfPiW998P4/j7RWi@pevik>

It's not clear if anything more than this is required for now.

Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
---

 doc/test-writing-guidelines.txt | 10 ++++++++++
 runtest/staging                 |  1 +
 2 files changed, 11 insertions(+)
 create mode 100644 runtest/staging

diff --git a/doc/test-writing-guidelines.txt b/doc/test-writing-guidelines.txt
index 1fa751ed5..8ca014d45 100644
--- a/doc/test-writing-guidelines.txt
+++ b/doc/test-writing-guidelines.txt
@@ -334,3 +334,13 @@ It's easier to maintain a '.gitignore' file per directory with tests, rather
 than having single file in the project root directory. This way, we don't have
 to update all the gitignore files when moving directories, and they get deleted
 automatically when a directory with tests is removed.
+
+7 Testing pre-release kernel features
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Tests for features not yet in a mainline kernel release are accepted. However
+they must only be added to the +staging+ runtest file. Once a feature is part
+of the stable kernel ABI the associated test must be moved out of staging.
+
+This is primarily to help test kernel RCs by avoiding the need to download
+separate LTP patchsets.
diff --git a/runtest/staging b/runtest/staging
new file mode 100644
index 000000000..ef1cdea15
--- /dev/null
+++ b/runtest/staging
@@ -0,0 +1 @@
+# Tests for features that are not yet in the stable kernel ABI
-- 
2.34.1


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-02-03 10:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211220180748.36A90A3B8E@relay2.suse.de>
2021-12-21 11:30 ` [LTP] [RFC PATCH] API: Allow testing of kernel features in development Richard Palethorpe via ltp
2021-12-21 12:14   ` Li Wang
2021-12-21 13:56     ` Richard Palethorpe
2021-12-21 17:56   ` Petr Vorel
2021-12-22  8:41     ` Jan Stancek
2021-12-22  8:44       ` Richard Palethorpe
2021-12-22  9:29       ` Petr Vorel
2022-01-05 15:57   ` Cyril Hrubis
2022-01-05 16:00     ` Cyril Hrubis
2022-01-10  8:09       ` Richard Palethorpe
2022-01-28 12:32         ` Petr Vorel
2022-02-03 10:18           ` Richard Palethorpe via ltp [this message]
2022-02-03 10:22             ` [LTP] [PATCH] Create policy for testing unstable kernel features Petr Vorel
2022-02-04  7:46             ` Jan Stancek
2022-02-08  8:18             ` Li Wang
2022-03-03 13:33               ` Petr Vorel
2022-06-14 12:31                 ` Petr Vorel
2022-06-14 13:13                   ` Cyril Hrubis
2022-06-16  8:25                     ` Petr Vorel

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=20220203101803.10204-1-rpalethorpe@suse.com \
    --to=ltp@lists.linux.it \
    --cc=rpalethorpe@suse.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.