From: <Tim.Bird@sony.com>
To: <sharinder@google.com>
Cc: <davidgow@google.com>, <brendanhiggins@google.com>,
<shuah@kernel.org>, <corbet@lwn.net>,
<linux-kselftest@vger.kernel.org>, <kunit-dev@googlegroups.com>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v2 5/7] Documentation: KUnit: Rework writing page to focus on writing tests
Date: Fri, 10 Dec 2021 17:16:13 +0000 [thread overview]
Message-ID: <BYAPR13MB250382B305D19D310AE45916FD719@BYAPR13MB2503.namprd13.prod.outlook.com> (raw)
In-Reply-To: <CAHLZCaHWK_oUbnFMeZ7yeCg1XtwTzb1qYNtG8qgi_dOm4ZNafQ@mail.gmail.com>
Thanks for responding to my review. I reviewed the remaining patches (v3 patches 6 and 7)
and found no issues.
-- Tim
> -----Original Message-----
> From: Harinder Singh <sharinder@google.com>
>
> Hello Tim,
>
> Thanks for providing review comments.
>
> Please see my comments below.
...
next prev parent reply other threads:[~2021-12-10 18:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 5:40 [PATCH v2 0/7] Documentation: KUnit: Rework KUnit documentation Harinder Singh
2021-12-07 5:40 ` [PATCH v2 1/7] Documentation: KUnit: Rewrite main page Harinder Singh
2021-12-07 17:11 ` Tim.Bird
2021-12-10 5:30 ` Harinder Singh
2021-12-07 5:40 ` [PATCH v2 2/7] Documentation: KUnit: Rewrite getting started Harinder Singh
2021-12-07 5:40 ` [PATCH v2 3/7] Documentation: KUnit: Added KUnit Architecture Harinder Singh
2021-12-07 17:24 ` Tim.Bird
2021-12-10 5:31 ` Harinder Singh
2021-12-10 23:08 ` Marco Elver
2021-12-16 6:12 ` Harinder Singh
2021-12-07 5:40 ` [PATCH v2 4/7] Documentation: kunit: Reorganize documentation related to running tests Harinder Singh
2021-12-07 17:33 ` Tim.Bird
2021-12-10 5:31 ` Harinder Singh
2021-12-07 5:40 ` [PATCH v2 5/7] Documentation: KUnit: Rework writing page to focus on writing tests Harinder Singh
2021-12-07 18:28 ` Tim.Bird
2021-12-10 5:31 ` Harinder Singh
2021-12-10 17:16 ` Tim.Bird [this message]
2021-12-16 5:43 ` Harinder Singh
2021-12-07 5:40 ` [PATCH v2 6/7] Documentation: KUnit: Restyle Test Style and Nomenclature page Harinder Singh
2021-12-07 18:46 ` Tim.Bird
2021-12-10 5:30 ` Harinder Singh
2021-12-07 5:40 ` [PATCH v2 7/7] Documentation: KUnit: Restyled Frequently Asked Questions Harinder Singh
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=BYAPR13MB250382B305D19D310AE45916FD719@BYAPR13MB2503.namprd13.prod.outlook.com \
--to=tim.bird@sony.com \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sharinder@google.com \
--cc=shuah@kernel.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;
as well as URLs for NNTP newsgroup(s).