From: Brendan Higgins <brendanhiggins@google.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: shuah <shuah@kernel.org>, SeongJae Park <sjpark@amazon.com>,
Jonathan Corbet <corbet@lwn.net>,
KUnit Development <kunit-dev@googlegroups.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
SeongJae Park <sjpark@amazon.de>
Subject: Re: [PATCH v6 0/6] Fix nits in the kunit
Date: Thu, 12 Dec 2019 13:31:56 -0800 [thread overview]
Message-ID: <CAFd5g46HjimaZB+_TJdy627p_jrBOrdav6+qDa4i_t4Kzmy8rQ@mail.gmail.com> (raw)
In-Reply-To: <20191212022711.10062-1-sjpark@amazon.de>
On Wed, Dec 11, 2019 at 6:27 PM SeongJae Park <sj38.park@gmail.com> wrote:
>
> This patchset contains trivial fixes for the kunit documentations and
> the wrapper python scripts.
>
>
> Baseline
> --------
>
> This patchset is based on 'kselftest/fixes' branch of
> linux-kselftest[1]. A complete tree is available at my repo:
> https://github.com/sjp38/linux/tree/kunit_fix/20191205_v6
Everything looks good to me. Shuah, feel free to pick this up at your
convenience.
SeongJae, Thanks for all your hard work on this. I really appreciate it!
next prev parent reply other threads:[~2019-12-12 21:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 2:27 [PATCH v6 0/6] Fix nits in the kunit SeongJae Park
2019-12-12 2:27 ` [PATCH v6 1/6] docs/kunit/start: Use in-tree 'kunit_defconfig' SeongJae Park
2019-12-12 2:27 ` [PATCH v6 2/6] kunit: Remove duplicated defconfig creation SeongJae Park
2019-12-12 2:27 ` [PATCH v6 3/6] kunit: Create default config in '--build_dir' SeongJae Park
2019-12-12 2:27 ` [PATCH v6 4/6] kunit: Place 'test.log' under the 'build_dir' SeongJae Park
2019-12-12 2:27 ` [PATCH v6 5/6] kunit: Rename 'kunitconfig' to '.kunitconfig' SeongJae Park
2019-12-12 2:27 ` [PATCH v6 6/6] kunit/kunit_tool_test: Test '--build_dir' option run SeongJae Park
2019-12-12 21:31 ` Brendan Higgins [this message]
2019-12-12 21:44 ` [PATCH v6 0/6] Fix nits in the kunit shuah
2019-12-19 23:37 ` shuah
2019-12-20 5:01 ` SeongJae Park
2019-12-20 5:18 ` SeongJae Park
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=CAFd5g46HjimaZB+_TJdy627p_jrBOrdav6+qDa4i_t4Kzmy8rQ@mail.gmail.com \
--to=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=kunit-dev@googlegroups.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.com \
--cc=sjpark@amazon.de \
/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).