From: Watson Wheeler <imnotamilkglass@gmail.com>
To: linux-mm@kvack.org
Cc: Watson Wheeler <git@tazy.dev>
Subject: [PATCH] lib/maple_tree: add missing spaces after switch keyword
Date: Tue, 23 Jun 2026 16:17:12 +1000 [thread overview]
Message-ID: <20260623061730.2024-1-git@tazy.dev> (raw)
Add the required space before the opening parenthesis in
switch statements to conform to kernel coding style.
Signed-off-by: Watson Wheeler <git@tazy.dev>
---
lib/maple_tree.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/lib/maple_tree.c b/lib/maple_tree.c
index e52876435b77..529acc056e55 100644
--- a/lib/maple_tree.c
+++ b/lib/maple_tree.c
@@ -6447,7 +6447,7 @@ static void mt_dump_range(unsigned long min, unsigned long max,
{
static const char spaces[] = " ";
- switch(format) {
+ switch (format) {
case mt_dump_hex:
if (min == max)
pr_info("%.*s%lx: ", depth * 2, spaces, min);
@@ -6489,7 +6489,7 @@ static void mt_dump_range64(const struct maple_tree *mt, void *entry,
pr_cont(" contents: ");
for (i = 0; i < MAPLE_RANGE64_SLOTS - 1; i++) {
- switch(format) {
+ switch (format) {
case mt_dump_hex:
pr_cont(PTR_FMT " %lX ", node->slot[i], node->pivot[i]);
break;
@@ -6517,7 +6517,7 @@ static void mt_dump_range64(const struct maple_tree *mt, void *entry,
if (last == max)
break;
if (last > max) {
- switch(format) {
+ switch (format) {
case mt_dump_hex:
pr_err("node " PTR_FMT " last (%lx) > max (%lx) at pivot %d!\n",
node, last, max, i);
@@ -6576,7 +6576,7 @@ static void mt_dump_arange64(const struct maple_tree *mt, void *entry,
if (last == max)
break;
if (last > max) {
- switch(format) {
+ switch (format) {
case mt_dump_hex:
pr_err("node " PTR_FMT " last (%lx) > max (%lx) at pivot %d!\n",
node, last, max, i);
--
2.47.3
reply other threads:[~2026-06-23 6:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260623061730.2024-1-git@tazy.dev \
--to=imnotamilkglass@gmail.com \
--cc=git@tazy.dev \
--cc=linux-mm@kvack.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