From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Diego Vieira <diego.daniel.professional@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@google.com>, Rae Moar <rmoar@google.com>,
<linux-kselftest@vger.kernel.org>, <kunit-dev@googlegroups.com>
Cc: <n@nfraprado.net>, <andrealmeid@riseup.net>, <vinicius@nukelet.com>
Subject: Re: [PATCH 1/1] lib/kfifo-test.c: add tests for the kfifo structure
Date: Mon, 22 Jul 2024 07:19:45 -0700 [thread overview]
Message-ID: <7fa38eba-97ca-4bbc-b585-f646a26a2c29@quicinc.com> (raw)
In-Reply-To: <20240722001804.8120-2-diego.daniel.professional@gmail.com>
On 7/21/24 17:18, Diego Vieira wrote:
> Add KUnit tests for the kfifo data structure.
> They test the vast majority of macros defined in the kfifo
> header (include/linux/kfifo.h).
>
> These are inspired by the existing tests for the 'list' doubly
> linked in lib/list-test.c [1].
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/lib/list-test.c
>
> Signed-off-by: Diego Vieira <diego.daniel.professional@gmail.com>
> ---
> lib/Kconfig.debug | 14 +++
> lib/Makefile | 1 +
> lib/kfifo-test.c | 222 ++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 237 insertions(+)
> create mode 100644 lib/kfifo-test.c
...
> +MODULE_LICENSE("GPL");
Since commit 1fffe7a34c89 ("script: modpost: emit a warning when the
description is missing") a module without a MODULE_DESCRIPTION() will
result in a warning with make W=1
Multiple developers, including myself, have been fixing the existing
warnings for 6.11 so please don't introduce a new one :)
/jeff
prev parent reply other threads:[~2024-07-22 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 0:18 [PATCH 0/1] Add KUnit tests for kfifo Diego Vieira
2024-07-22 0:18 ` [PATCH 1/1] lib/kfifo-test.c: add tests for the kfifo structure Diego Vieira
2024-07-22 14:19 ` Jeff Johnson [this message]
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=7fa38eba-97ca-4bbc-b585-f646a26a2c29@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@riseup.net \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=diego.daniel.professional@gmail.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=n@nfraprado.net \
--cc=rmoar@google.com \
--cc=vinicius@nukelet.com \
/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