From: Sander Vanheule <sander@svanheule.net>
To: Yury Norov <yury.norov@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Brendan Higgins <brendan.higgins@linux.dev>,
David Gow <davidgow@google.com>,
linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com
Cc: "Maíra Canal" <mairacanal@riseup.net>,
linux-kernel@vger.kernel.org,
"Sander Vanheule" <sander@svanheule.net>
Subject: [PATCH v3 5/5] lib/cpumask_kunit: add tests file to MAINTAINERS
Date: Tue, 23 Aug 2022 08:12:23 +0200 [thread overview]
Message-ID: <a4d878c1a0f95837f4d2b6db1e3c9248044e6002.1661234636.git.sander@svanheule.net> (raw)
In-Reply-To: <cover.1661234636.git.sander@svanheule.net>
cpumask related files are listed under the BITMAP API section, so the
file with tests for cpumask should be added to that list.
Signed-off-by: Sander Vanheule <sander@svanheule.net>
Reviewed-by: David Gow <davidgow@google.com>
Acked-by: Yury Norov <yury.norov@gmail.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f512b430c7cb..0f41174be0d3 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3612,6 +3612,7 @@ F: include/linux/find.h
F: include/linux/nodemask.h
F: lib/bitmap.c
F: lib/cpumask.c
+F: lib/cpumask_kunit.c
F: lib/find_bit.c
F: lib/find_bit_benchmark.c
F: lib/test_bitmap.c
--
2.37.2
next prev parent reply other threads:[~2022-08-23 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 6:12 [PATCH v3 0/5] cpumask: KUnit test suite fixes and improvements Sander Vanheule
2022-08-23 6:12 ` [PATCH v3 1/5] lib/test_cpumask: drop cpu_possible_mask full test Sander Vanheule
2022-08-23 6:12 ` [PATCH v3 2/5] lib/test_cpumask: fix cpu_possible_mask last test Sander Vanheule
2022-08-23 6:12 ` [PATCH v3 3/5] lib/test_cpumask: follow KUnit style guidelines Sander Vanheule
2022-08-23 6:12 ` [PATCH v3 4/5] lib/cpumask_kunit: log mask contents Sander Vanheule
2022-08-23 6:12 ` Sander Vanheule [this message]
2022-08-24 16:09 ` [PATCH v3 0/5] cpumask: KUnit test suite fixes and improvements Yury Norov
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=a4d878c1a0f95837f4d2b6db1e3c9248044e6002.1661234636.git.sander@svanheule.net \
--to=sander@svanheule.net \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mairacanal@riseup.net \
--cc=yury.norov@gmail.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
all inboxes | Powered by JetHome®