From: Kees Cook <keescook@chromium.org> To: David Gow <davidgow@google.com> Cc: shuah@kernel.org, brendanhiggins@google.com, akpm@linux-foundation.org, linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com, linux-kernel@vger.kernel.org, dan.carpenter@oracle.com Subject: Re: [PATCH linux-kselftest/test v6] lib/list-test: add a test for the 'list' doubly linked list Date: Thu, 31 Oct 2019 11:50:58 -0700 [thread overview] Message-ID: <201910311147.FA6A822@keescook> (raw) In-Reply-To: <20191024224631.118656-1-davidgow@google.com> On Thu, Oct 24, 2019 at 03:46:31PM -0700, David Gow wrote: > diff --git a/MAINTAINERS b/MAINTAINERS > index 7ef985e01457..f3d0c6e42b97 100644 > --- a/MAINTAINERS > +++ b/MAINTAINERS > @@ -9504,6 +9504,13 @@ F: Documentation/misc-devices/lis3lv02d.rst > F: drivers/misc/lis3lv02d/ > F: drivers/platform/x86/hp_accel.c > > +LIST KUNIT TEST > +M: David Gow <davidgow@google.com> > +L: linux-kselftest@vger.kernel.org > +L: kunit-dev@googlegroups.com > +S: Maintained > +F: lib/list-test.c Should KUnit be the first name here? Then all KUnit tests appear in the same location in the MAINTAINERS file, or should it be like it is here, so that KUnit tests are close to the same-named area? > + > LIVE PATCHING > M: Josh Poimboeuf <jpoimboe@redhat.com> > M: Jiri Kosina <jikos@kernel.org> > diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug > index a3017a5dadcd..6c1be6181e38 100644 > --- a/lib/Kconfig.debug > +++ b/lib/Kconfig.debug > @@ -1961,6 +1961,24 @@ config SYSCTL_KUNIT_TEST > > If unsure, say N. > > +config LIST_KUNIT_TEST Similarly for the Kconfig name. (Also aren't KUNIT and TEST redundant?) config KUNIT_LIST ? config LIST_KUNIT > --- a/lib/Makefile > +++ b/lib/Makefile > @@ -292,3 +292,6 @@ obj-$(CONFIG_GENERIC_LIB_MULDI3) += muldi3.o > obj-$(CONFIG_GENERIC_LIB_CMPDI2) += cmpdi2.o > obj-$(CONFIG_GENERIC_LIB_UCMPDI2) += ucmpdi2.o > obj-$(CONFIG_OBJAGG) += objagg.o > + > +# KUnit tests > +obj-$(CONFIG_LIST_KUNIT_TEST) += list-test.o And again, list-kunit.o? Other things have -test (or more commonly _test) suffixes. (So maybe list_kunit.o?) But as I said last time, I'll live with whatever, I'd just like a documented best-practice with a reasonable rationale. :) -- Kees Cook
next prev parent reply other threads:[~2019-10-31 18:51 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-24 22:46 David Gow 2019-10-29 13:00 ` shuah 2019-10-30 8:02 ` David Gow 2019-10-30 10:42 ` Dan Carpenter 2019-10-30 16:27 ` shuah 2019-10-30 16:35 ` Brendan Higgins 2019-10-30 17:18 ` Joe Perches 2019-10-31 8:51 ` Brendan Higgins 2019-10-31 10:07 ` Joe Perches 2019-10-31 10:20 ` Dan Carpenter 2019-10-30 18:46 ` Dan Carpenter 2019-10-30 19:15 ` Joe Perches 2019-10-31 6:59 ` Dan Carpenter 2019-11-01 10:50 ` Rasmus Villemoes 2019-10-30 19:12 ` Dan Carpenter 2019-10-30 19:23 ` Joe Perches 2019-10-31 7:12 ` David Gow 2019-10-31 7:42 ` Dan Carpenter 2019-11-01 16:49 ` shuah 2019-10-30 16:31 ` Joe Perches 2019-10-31 18:50 ` Kees Cook [this message] 2019-11-01 10:25 ` 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=201910311147.FA6A822@keescook \ --to=keescook@chromium.org \ --cc=akpm@linux-foundation.org \ --cc=brendanhiggins@google.com \ --cc=dan.carpenter@oracle.com \ --cc=davidgow@google.com \ --cc=kunit-dev@googlegroups.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-kselftest@vger.kernel.org \ --cc=shuah@kernel.org \ --subject='Re: [PATCH linux-kselftest/test v6] lib/list-test: add a test for the '\''list'\'' doubly linked list' \ /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
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).