From: David Gow <davidgow@google.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Brendan Higgins <brendanhiggins@google.com>,
KUnit Development <kunit-dev@googlegroups.com>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 1/3] lib/list_kunit: Follow new file name convention for KUnit tests
Date: Fri, 16 Oct 2020 12:53:46 +0800 [thread overview]
Message-ID: <CABVgOSkKhpObfYPn2vYTcTdjDfmTyksWzUyRSuSShbkPCWLorA@mail.gmail.com> (raw)
In-Reply-To: <20201015184416.38999-1-andriy.shevchenko@linux.intel.com>
On Fri, Oct 16, 2020 at 2:44 AM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> Follow new file name convention for the KUnit tests.
> Since we have lib/*test*.c in a few variations,
> use 'kunit' suffix to distinguish usual test cases
> with KUnit-based ones.
>
> Cc: David Gow <davidgow@google.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Thanks! You've saved me the work of doing this myself. :-)
Reviewed-by: David Gow <davidgow@google.com>
prev parent reply other threads:[~2020-10-16 4:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 18:44 [PATCH v2 1/3] lib/list_kunit: Follow new file name convention for KUnit tests Andy Shevchenko
2020-10-15 18:44 ` [PATCH v2 2/3] lib/linear_ranges_kunit: " Andy Shevchenko
2020-10-16 5:02 ` David Gow
2020-10-16 9:29 ` Andy Shevchenko
2020-10-17 6:57 ` David Gow
2020-10-16 10:38 ` Mark Brown
2020-10-16 11:03 ` Andy Shevchenko
2020-10-16 11:10 ` Andy Shevchenko
2020-10-16 11:12 ` Mark Brown
2020-10-15 18:44 ` [PATCH v2 3/3] lib/bits_kunit: " Andy Shevchenko
2020-10-16 5:07 ` David Gow
2020-10-16 4:53 ` David Gow [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=CABVgOSkKhpObfYPn2vYTcTdjDfmTyksWzUyRSuSShbkPCWLorA@mail.gmail.com \
--to=davidgow@google.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brendanhiggins@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=skhan@linuxfoundation.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).