From: Jonathan Corbet <corbet@lwn.net>
To: Harinder Singh <sharinder@google.com>,
davidgow@google.com, brendanhiggins@google.com, shuah@kernel.org
Cc: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
tim.bird@sony.com, elver@google.com,
Harinder Singh <sharinder@google.com>
Subject: Re: [PATCH v6 0/7] Documentation: KUnit: Rework KUnit documentation
Date: Thu, 23 Dec 2021 12:49:59 -0700 [thread overview]
Message-ID: <87v8zfdrtk.fsf@meer.lwn.net> (raw)
In-Reply-To: <20211217044911.798817-1-sharinder@google.com>
Harinder Singh <sharinder@google.com> writes:
> The KUnit documentation was not very organized. There was little
> information related to KUnit architecture and the importance of unit
> testing.
>
> Add some new pages, expand and reorganize the existing documentation.
> Reword pages to make information and style more consistent.
Series applied, thanks.
jon
prev parent reply other threads:[~2021-12-23 19:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 4:49 [PATCH v6 0/7] Documentation: KUnit: Rework KUnit documentation Harinder Singh
2021-12-17 4:49 ` [PATCH v6 1/7] Documentation: KUnit: Rewrite main page Harinder Singh
2021-12-17 4:49 ` [PATCH v6 2/7] Documentation: KUnit: Rewrite getting started Harinder Singh
2021-12-17 4:49 ` [PATCH v6 3/7] Documentation: KUnit: Added KUnit Architecture Harinder Singh
2021-12-17 10:50 ` Marco Elver
2021-12-23 19:48 ` Jonathan Corbet
2021-12-17 4:49 ` [PATCH v6 4/7] Documentation: kunit: Reorganize documentation related to running tests Harinder Singh
2021-12-17 4:49 ` [PATCH v6 5/7] Documentation: KUnit: Rework writing page to focus on writing tests Harinder Singh
2021-12-17 4:49 ` [PATCH v6 6/7] Documentation: KUnit: Restyle Test Style and Nomenclature page Harinder Singh
2021-12-17 4:49 ` [PATCH v6 7/7] Documentation: KUnit: Restyled Frequently Asked Questions Harinder Singh
2021-12-17 5:09 ` [PATCH v6 0/7] Documentation: KUnit: Rework KUnit documentation Brendan Higgins
2021-12-23 19:49 ` Jonathan Corbet [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=87v8zfdrtk.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=elver@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 \
--cc=tim.bird@sony.com \
/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