From: Shuah Khan <skhan@linuxfoundation.org>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
Arpitha Raghunandan <98.arpi@gmail.com>
Cc: brendanhiggins@google.com, elver@google.com, yzaikin@google.com,
adilger.kernel@dilger.ca, Tim.Bird@sony.com, davidgow@google.com,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-ext4@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v9 2/2] fs: ext4: Modify inode-test.c to use KUnit parameterized testing feature
Date: Wed, 2 Dec 2020 15:59:08 -0700 [thread overview]
Message-ID: <161a322e-e7a0-1b2b-d321-4f2871c31e0a@linuxfoundation.org> (raw)
In-Reply-To: <20201202160742.GB390058@mit.edu>
On 12/2/20 9:07 AM, Theodore Y. Ts'o wrote:
> On Mon, Nov 16, 2020 at 11:11:50AM +0530, Arpitha Raghunandan wrote:
>> Modify fs/ext4/inode-test.c to use the parameterized testing
>> feature of KUnit.
>>
>> Signed-off-by: Arpitha Raghunandan <98.arpi@gmail.com>
>> Signed-off-by: Marco Elver <elver@google.com>
>
> Acked-by: Theodore Ts'o <tytso@mit.edu>
>
Thanks Ted.
-- Shuah
next prev parent reply other threads:[~2020-12-02 22:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 5:40 [PATCH v9 1/2] kunit: Support for Parameterized Testing Arpitha Raghunandan
2020-11-16 5:41 ` [PATCH v9 2/2] fs: ext4: Modify inode-test.c to use KUnit parameterized testing feature Arpitha Raghunandan
2020-11-16 8:51 ` Marco Elver
2020-11-17 7:22 ` David Gow
2020-12-01 20:30 ` Iurii Zaikin
2020-12-02 16:07 ` Theodore Y. Ts'o
2020-12-02 22:59 ` Shuah Khan [this message]
2020-11-16 8:53 ` [PATCH v9 1/2] kunit: Support for Parameterized Testing Marco Elver
2020-11-17 7:20 ` David Gow
2020-11-23 13:08 ` Marco Elver
2020-11-24 7:25 ` David Gow
2020-11-24 8:02 ` Marco Elver
2020-11-30 22:22 ` Brendan Higgins
2020-12-01 22:28 ` Shuah Khan
2020-12-01 23:31 ` Marco Elver
2020-12-02 22:58 ` Shuah Khan
2020-12-02 16:02 ` Theodore Y. Ts'o
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=161a322e-e7a0-1b2b-d321-4f2871c31e0a@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=98.arpi@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=adilger.kernel@dilger.ca \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=elver@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yzaikin@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;
as well as URLs for NNTP newsgroup(s).