From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com
Cc: Jonathan Corbet <corbet@lwn.net>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@google.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Khalid Masum <khalid.masum.92@gmail.com>,
Sadiya Kazi <sadiyakazi@google.com>
Subject: Re: [PATCH 7/7] Documentation: kunit: rewrite usage
Date: Sun, 23 Oct 2022 20:08:05 +0700 [thread overview]
Message-ID: <d6fbe2e6-6e5a-823e-462d-19a8e18fbb40@gmail.com> (raw)
In-Reply-To: <20221023125414.60961-8-bagasdotme@gmail.com>
On 10/23/22 19:54, Bagas Sanjaya wrote:
> Rewrite the documentation for clarity. Major points:
>
> * Switch to third person point of view
> * Briefly describe code examples before giving them out
> * Use "base" and "derived" terminology on class inheritance
>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Oops, duplicate patch sent. Please ignore this series.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2022-10-23 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 12:54 [PATCH 0/7] KUnit documentation rewording Bagas Sanjaya
2022-10-23 12:54 ` [PATCH 1/7] Documentation: kunit: rewrite "Writing Your First Test" section Bagas Sanjaya
2022-10-23 12:54 ` [PATCH 2/7] Documentation: kunit: align instruction code blocks Bagas Sanjaya
2022-10-23 12:54 ` [PATCH 3/7] Documentation: kunit: rewrite the rest of "Getting Started" documentation Bagas Sanjaya
2022-11-11 19:46 ` Daniel Latypov
2022-10-23 12:54 ` [PATCH 4/7] Documentation: kunit: move introduction to its own document Bagas Sanjaya
2022-10-23 12:54 ` [PATCH 5/7] Documentation: kunit: rewrite "Running tests with kunit_tool" Bagas Sanjaya
2022-10-23 12:54 ` [PATCH 6/7] Documentation: kunit: rewrite "Run Tests without kunit_tool" Bagas Sanjaya
2022-10-23 12:54 ` [PATCH 7/7] Documentation: kunit: rewrite usage Bagas Sanjaya
2022-10-23 13:08 ` Bagas Sanjaya [this message]
2022-10-23 12:54 ` [PATCH 7/7] Documentation: kunit: rewrite "Writing tests" Bagas Sanjaya
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=d6fbe2e6-6e5a-823e-462d-19a8e18fbb40@gmail.com \
--to=bagasdotme@gmail.com \
--cc=brendan.higgins@linux.dev \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=khalid.masum.92@gmail.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=lukas.bulwahn@gmail.com \
--cc=sadiyakazi@google.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