From: frowand.list@gmail.com
To: Jonathan Corbet <corbet@lwn.net>, David Gow <davidgow@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
Tim.Bird@sony.com, Brendan Higgins <brendanhiggins@google.com>
Cc: rmr167@gmail.com, guillaume.tucker@collabora.com,
dlatypov@google.com, kernelci@groups.io,
kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 1/2] Documentation: dev-tools: KTAP spec change version to 2-rc
Date: Wed, 16 Mar 2022 15:26:21 -0500 [thread overview]
Message-ID: <20220316202622.324866-2-frowand.list@gmail.com> (raw)
In-Reply-To: <20220316202622.324866-1-frowand.list@gmail.com>
From: Frank Rowand <frank.rowand@sony.com>
Prepare KTAP Specification for the process of creating Version 2.
The version will remain 2-rc until the final commit to complete
Version 2.
Signed-off-by: Frank Rowand <frank.rowand@sony.com>
---
Documentation/dev-tools/ktap.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/dev-tools/ktap.rst b/Documentation/dev-tools/ktap.rst
index 5ee735c6687f..37b5dc61bfb8 100644
--- a/Documentation/dev-tools/ktap.rst
+++ b/Documentation/dev-tools/ktap.rst
@@ -1,7 +1,7 @@
.. SPDX-License-Identifier: GPL-2.0
===================================================
-The Kernel Test Anything Protocol (KTAP), version 1
+The Kernel Test Anything Protocol (KTAP), version 2-rc
===================================================
TAP, or the Test Anything Protocol is a format for specifying test results used
--
Frank Rowand <frank.rowand@sony.com>
next prev parent reply other threads:[~2022-03-16 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 20:26 [RFC PATCH 0/2] Documentation: dev-tools: begin KTAP spec v2 process frowand.list
2022-03-16 20:26 ` frowand.list [this message]
2022-03-17 8:43 ` [RFC PATCH 1/2] Documentation: dev-tools: KTAP spec change version to 2-rc David Gow
2022-04-22 23:25 ` Frank Rowand
2022-03-16 20:26 ` [RFC PATCH 2/2] Documentation: dev-tools: use literal block instead of code-block frowand.list
2022-03-17 8:43 ` David Gow
2022-04-22 23:10 ` Frank Rowand
2022-04-28 18:35 ` Jonathan Corbet
2022-03-17 8:42 ` [RFC PATCH 0/2] Documentation: dev-tools: begin KTAP spec v2 process David Gow
2022-04-22 23:16 ` Frank Rowand
2022-04-23 7:53 ` David Gow
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=20220316202622.324866-2-frowand.list@gmail.com \
--to=frowand.list@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=guillaume.tucker@collabora.com \
--cc=keescook@chromium.org \
--cc=kernelci@groups.io \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rmr167@gmail.com \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®