From: Kees Cook <keescook@chromium.org>
To: frowand.list@gmail.com
Cc: Jonathan Corbet <corbet@lwn.net>, David Gow <davidgow@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Rae Moar <rmoar@google.com>,
Tim.Bird@sony.com, Brendan Higgins <brendanhiggins@google.com>,
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 v4 1/2] Documentation: dev-tools: clarify KTAP specification wording
Date: Thu, 10 Feb 2022 09:43:12 -0800 [thread overview]
Message-ID: <202202100942.A8206C0@keescook> (raw)
In-Reply-To: <20220210023519.3221051-2-frowand.list@gmail.com>
On Wed, Feb 09, 2022 at 08:35:18PM -0600, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> Add the spec version to the title line.
>
> Explain likely source of "Unknown lines".
>
> "Unknown lines" in nested tests are optionally indented.
>
> Add "Unknown lines" items to differences between TAP & KTAP list
>
> Reviewed-by: Tim Bird <Tim.Bird@sony.com>
> Reviewed-by: David Gow <davidgow@google.com>
> Reviewed-by: Shuah Khan <skhan@linuxfoundation.org>
> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
Thanks for nailing this down!
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
next prev parent reply other threads:[~2022-02-10 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 2:35 [PATCH v4 0/2] Documentation: dev-tools: clarify KTAP specification wording frowand.list
2022-02-10 2:35 ` [PATCH v4 1/2] " frowand.list
2022-02-10 17:43 ` Kees Cook [this message]
2022-02-10 2:35 ` [PATCH v4 2/2] Documentation: dev-tools: fix KTAP specification build warnings frowand.list
2022-02-10 7:44 ` David Gow
2022-02-10 17:25 ` Shuah Khan
2022-02-10 17:43 ` Kees Cook
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=202202100942.A8206C0@keescook \
--to=keescook@chromium.org \
--cc=Tim.Bird@sony.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=frowand.list@gmail.com \
--cc=guillaume.tucker@collabora.com \
--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=rmoar@google.com \
--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