archive mirror
 help / color / mirror / Atom feed
From: David Gow via Linux-kernel-mentees <>
To: Andy Shevchenko <>
Cc: Arpitha Raghunandan <>,
	Brendan Higgins <>,
	Linux Kernel Mailing List <>,
	Andy Shevchenko <>,,
	KUnit Development <>
Subject: Re: [Linux-kernel-mentees] [PATCH] lib: Convert test_hexdump.c to KUnit
Date: Sat, 8 Aug 2020 05:33:09 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Aug 6, 2020 at 5:53 PM Andy Shevchenko
<> wrote:
> On Thu, Aug 6, 2020 at 12:48 PM Arpitha Raghunandan <> wrote:
> >
> > Converts test lib/test_hexdump.c to KUnit.
> > More information about KUnit can be found at
> >
> > KUnit provides a common framework for unit tests in the kernel.
> > -config TEST_HEXDUMP
> > -       tristate "Test functions located in the hexdump module at runtime"
> We have a nice collection of tests starting with TEST_ in the
> configuration, now it's gone.
> I'm strongly against this change.
> Code itself okay, but without addressing above - NAK.

This change is to make the test naming compliant with the proposed
KUnit test naming guidelines:

The hope is that tests built on KUnit will all end up with the same
[x]_KUNIT_TEST config options (which at least preserves the
consistency of the test naming, even if they'll not all sort
together), and should make it easier for people to know that the test
results will be in a common format, and that the test can also be run
using the KUnit tools.

The naming guidelines haven't been upstreamed yet, though, so we'd
definitely appreciate input on that thread if you've got comments more
broadly than for this particular patch. Ultimately, I don't think it
matters too much what we end up using, but having some consistency is
the goal.
Linux-kernel-mentees mailing list

  reply	other threads:[~2020-08-07 21:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-06  9:44 [Linux-kernel-mentees] [PATCH] lib: Convert test_hexdump.c to KUnit Arpitha Raghunandan
2020-08-06  9:52 ` Andy Shevchenko
2020-08-07 21:33   ` David Gow via Linux-kernel-mentees [this message]
2020-08-06 10:05 ` Andy Shevchenko
2020-08-09 15:11   ` Arpitha Raghunandan

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \

* 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).