From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kselftest@vger.kernel.org,
Brendan Higgins <brendanhiggins@google.com>,
kunit-dev@googlegroups.com,
Shuah Khan <skhan@linuxfoundation.org>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Subject: Re: [PATCH v2 2/3] lib/linear_ranges_kunit: Follow new file name convention for KUnit tests
Date: Fri, 16 Oct 2020 14:03:44 +0300 [thread overview]
Message-ID: <20201016110344.GJ4077@smile.fi.intel.com> (raw)
In-Reply-To: <20201016103841.GA5274@sirena.org.uk>
On Fri, Oct 16, 2020 at 11:38:41AM +0100, Mark Brown wrote:
> On Thu, Oct 15, 2020 at 09:44:15PM +0300, Andy Shevchenko 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.
>
> I'm missing the rest of this series - what's the story with dependencies
> here?
There is a dependency in Makefile. Do you want me to send a new version with
Cc'ing you all?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-10-16 11:02 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 [this message]
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 ` [PATCH v2 1/3] lib/list_kunit: " David Gow
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=20201016110344.GJ4077@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brendanhiggins@google.com \
--cc=broonie@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.