From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vitor Massaru Iha <vitor@massaru.org>
Cc: fkostenzer@live.at, torvalds@linux-foundation.org,
brendanhiggins@google.com, linux-kernel@vger.kernel.org,
paul.gortmaker@windriver.com, geert@linux-m68k.org,
linux-kselftest@vger.kernel.org, tglx@linutronix.de,
linux-kernel-mentees@lists.linuxfoundation.org,
akpm@linux-foundation.org, kunit-dev@googlegroups.com
Subject: Re: [Linux-kernel-mentees] [PATCH] lib: kunit: Convert test_sort to KUnit test
Date: Thu, 23 Jul 2020 11:04:44 +0300 [thread overview]
Message-ID: <20200723080444.GE3703480@smile.fi.intel.com> (raw)
In-Reply-To: <20200723000807.171940-1-vitor@massaru.org>
On Wed, Jul 22, 2020 at 09:08:07PM -0300, Vitor Massaru Iha wrote:
> This adds the conversion of the test_sort.c to KUnit test.
>
> Please apply this commit first (linux-kselftest/kunit-fixes):
> 3f37d14b8a3152441f36b6bc74000996679f0998 kunit: kunit_config: Fix parsing of CONFIG options with space
...
> lib/{test_sort.c => sort_kunit.c} | 31 +++++++++++++++----------------
Is it established practice to put kunit as a suffix?
For me much better to do
ls .../test* # and note shell completions
then drop shell completions and always do something like
ls .../*_kunit.[cSsh]
Consider this, please.
P.S. Same question to KUnit folks.
--
With Best Regards,
Andy Shevchenko
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-07-23 8:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 0:08 [Linux-kernel-mentees] [PATCH] lib: kunit: Convert test_sort to KUnit test Vitor Massaru Iha
2020-07-23 8:04 ` Andy Shevchenko [this message]
2020-07-23 12:32 ` Vitor Massaru Iha
2020-07-24 16:05 ` kernel test robot
2020-07-24 23:43 ` kernel test robot
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=20200723080444.GE3703480@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=brendanhiggins@google.com \
--cc=fkostenzer@live.at \
--cc=geert@linux-m68k.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vitor@massaru.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