From: Jonathan Corbet <corbet@lwn.net>
To: Marco Elver <elver@google.com>, Harinder Singh <sharinder@google.com>
Cc: davidgow@google.com, brendanhiggins@google.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Tim.Bird@sony.com
Subject: Re: [PATCH v6 3/7] Documentation: KUnit: Added KUnit Architecture
Date: Thu, 23 Dec 2021 12:48:33 -0700 [thread overview]
Message-ID: <87zgordrvy.fsf@meer.lwn.net> (raw)
In-Reply-To: <CANpmjNMz7nh7Eo97p-ikdE6cyTu_Vge_RJktj68BpC9QHqE7iw@mail.gmail.com>
Marco Elver <elver@google.com> writes:
> On Fri, 17 Dec 2021 at 05:49, Harinder Singh <sharinder@google.com> wrote:
>>
>> Describe the components of KUnit and how the kernel mode parts
>> interact with kunit_tool.
>>
>> Signed-off-by: Harinder Singh <sharinder@google.com>
>
> Acked-by: Marco Elver <elver@google.com>
>
> For the .svg file, I think per
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin
> at least my Signed-off-by is required, but probably also my
> Co-developed-by? In any case my SOB for kunit_suitememorydiagram.svg
> is hereby given:
>
> Signed-off-by: Marco Elver <elver@google.com>
This is important; Harinder, please try to be sure to credit things
properly; I'll add this tag to the patch.
Thanks,
jon
next prev parent reply other threads:[~2021-12-23 19:48 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 [this message]
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
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=87zgordrvy.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=Tim.Bird@sony.com \
--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 \
/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).