mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 0/2] Documentation: dev-tools: begin KTAP spec v2 process
Date: Wed, 16 Mar 2022 15:26:20 -0500	[thread overview]
Message-ID: <20220316202622.324866-1-frowand.list@gmail.com> (raw)

From: Frank Rowand <frank.rowand@sony.com>

An August 2021 RFC patch [1] to create the KTAP Specification resulted in
some discussion of possible items to add to the specification.
The conversation ended without completing the document.

Progress resumed with a December 2021 RFC patch [2] to add a KTAP
Specification file (Version 1) to the Linux kernel.  Many of the
suggestions from the August 2021 discussion were not included in
Version 1.  This patch series is intended to revisit some of the
suggestions from the August 2021 discussion.

Patch 1 changes the Specification version to "2-rc" to indicate
that following patches are not yet accepted into a final version 2.

Patch 2 is an example of a simple change to the Specification.  The
change does not change the content of the Specification, but updates
a formatting directive as suggested by the Documentation maintainer.

I intend to take some specific suggestions from the August 2021
discussion to create stand-alone RFC patches to the Specification
instead of adding them as additional patches in this series.  The
intent is to focus discussion on a single area of the Specification
in each patch email thread.

[1] https://lore.kernel.org/r/CA+GJov6tdjvY9x12JsJT14qn6c7NViJxqaJk+r-K1YJzPggFDQ@mail.gmail.com
[2] https://lore.kernel.org/r/20211207190251.18426-1-davidgow@google.com

Frank Rowand (2):
  Documentation: dev-tools: KTAP spec change version to 2-rc
  Documentation: dev-tools: use literal block instead of code-block

 Documentation/dev-tools/ktap.rst | 20 +++++++++-----------
 1 file changed, 9 insertions(+), 11 deletions(-)

-- 
Frank Rowand <frank.rowand@sony.com>


             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 frowand.list [this message]
2022-03-16 20:26 ` [RFC PATCH 1/2] Documentation: dev-tools: KTAP spec change version to 2-rc frowand.list
2022-03-17  8:43   ` 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-1-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®