From: Brendan Higgins <brendanhiggins@google.com>
To: David Gow <davidgow@google.com>
Cc: shuah@kernel.org, akpm@linux-foundation.org,
keescook@chromium.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/list-test: add a test for the 'list' doubly linked list
Date: Tue, 8 Oct 2019 10:48:37 -0700 [thread overview]
Message-ID: <20191008174837.GA155928@google.com> (raw)
In-Reply-To: <20191007213633.92565-1-davidgow@google.com>
On Mon, Oct 07, 2019 at 02:36:33PM -0700, David Gow wrote:
> This change adds a KUnit test for the kernel doubly linked list
> implementation in include/linux/list.h
>
> Note that, at present, it only tests the list_ types (not the
> singly-linked hlist_), and does not yet test all of the
> list_for_each_entry* macros (and some related things like
> list_prepare_entry).
>
> This change depends on KUnit, so should be merged via the 'test' branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/log/?h=test
>
> Signed-off-by: David Gow <davidgow@google.com>
> ---
> lib/Kconfig.debug | 12 +
> lib/Makefile | 3 +
> lib/list-test.c | 711 ++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 726 insertions(+)
> create mode 100644 lib/list-test.c
Also, I think it might be good to make a MAINTAINERs entry for this
test.
Cheers!
next prev parent reply other threads:[~2019-10-08 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 21:36 [PATCH] lib/list-test: add a test for the 'list' doubly linked list David Gow
2019-10-07 21:58 ` Brendan Higgins
2019-10-08 1:03 ` Kees Cook
2019-10-08 23:30 ` David Gow
2019-10-08 3:29 ` Kees Cook
2019-10-08 17:48 ` Brendan Higgins [this message]
2019-10-08 18:15 ` Kees Cook
2019-10-08 22:59 ` Brendan Higgins
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=20191008174837.GA155928@google.com \
--to=brendanhiggins@google.com \
--cc=akpm@linux-foundation.org \
--cc=davidgow@google.com \
--cc=keescook@chromium.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.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).