From: Frank Rowand <frowand.list@gmail.com>
To: 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: Jonathan Corbet <corbet@lwn.net>,
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: Re: [PATCH v3 0/2] begin KTAP spec v2 process
Date: Tue, 30 Aug 2022 17:16:33 -0500 [thread overview]
Message-ID: <63b5fa8c-9fb8-b2ff-3f15-cc8649224f06@gmail.com> (raw)
In-Reply-To: <20220829233150.3564612-1-frowand.list@gmail.com>
On 8/29/22 18:31, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> The process to create version 2 of the KTAP Specification is documented
> in email discussions. I am attempting to capture this information at
>
> https://elinux.org/Test_Results_Format_Notes#KTAP_version_2
>
> I am already not following the suggested process, which says:
> "...please try to follow this principal of one major topic per email
> thread." I think that is ok in this case because the two patches
> are related and (hopefully) not controversial.
>
> Changes since patch version 2:
> - correct version 1 change text
> - version 1 patch 2/2 had not yet been applied when I created version 2,
> refresh version 2 patch 2/2 for new context
>
> Changes since patch version 1:
> - drop patch 2/2. Jonathan Corbet has already applied this patch
> into version 1 of the Specification
> - add new patch 2/2
>
> Frank Rowand (2):
> ktap_v2: change version to 2-rc in KTAP specification
> ktap_v2: change "version 1" to "version 2" in examples
>
> Documentation/dev-tools/ktap.rst | 25 +++++++++++++------------
> 1 file changed, 13 insertions(+), 12 deletions(-)
>
The process for developing KTAP spec v2 and the status of proposals
and accepted patches can be found at:
https://elinux.org/Test_Results_Format_Notes#KTAP_version_2
prev parent reply other threads:[~2022-08-30 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 23:31 [PATCH v3 0/2] begin KTAP spec v2 process frowand.list
2022-08-29 23:31 ` [PATCH v3 1/2] ktap_v2: change version to 2-rc in KTAP specification frowand.list
2022-08-30 1:48 ` Bagas Sanjaya
2022-08-30 15:04 ` Frank Rowand
2022-08-30 12:54 ` Matthew Wilcox
2022-08-30 15:06 ` Frank Rowand
2022-08-29 23:31 ` [PATCH v3 2/2] ktap_v2: change "version 1" to "version 2" in examples frowand.list
2022-08-30 22:16 ` Frank Rowand [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=63b5fa8c-9fb8-b2ff-3f15-cc8649224f06@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