From: Markus Elfring <Markus.Elfring@web.de>
To: linux-gpio@vger.kernel.org, kernel-janitors@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] pinctrl: core: Use seq_putc() in three functions
Date: Sat, 13 Jul 2024 16:15:28 +0200 [thread overview]
Message-ID: <3a52f0c5-85c5-4077-b6cd-504cc5383817@web.de> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Sat, 13 Jul 2024 16:10:31 +0200
Single characters (line breaks) should be put into a sequence.
Thus use the corresponding function “seq_putc”.
This issue was transformed by using the Coccinelle software.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
drivers/pinctrl/core.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/pinctrl/core.c b/drivers/pinctrl/core.c
index 314ab93d7691..6d61101f488a 100644
--- a/drivers/pinctrl/core.c
+++ b/drivers/pinctrl/core.c
@@ -1707,7 +1707,7 @@ static int pinctrl_pins_show(struct seq_file *s, void *what)
if (ops->pin_dbg_show)
ops->pin_dbg_show(pctldev, s, pin);
- seq_puts(s, "\n");
+ seq_putc(s, '\n');
}
mutex_unlock(&pctldev->mutex);
@@ -1751,7 +1751,7 @@ static int pinctrl_groups_show(struct seq_file *s, void *what)
}
seq_printf(s, "pin %d (%s)\n", pins[i], pname);
}
- seq_puts(s, "\n");
+ seq_putc(s, '\n');
}
selector++;
}
@@ -1814,7 +1814,7 @@ static int pinctrl_devices_show(struct seq_file *s, void *what)
seq_puts(s, "yes");
else
seq_puts(s, "no");
- seq_puts(s, "\n");
+ seq_putc(s, '\n');
}
mutex_unlock(&pinctrldev_list_mutex);
--
2.45.2
reply other threads:[~2024-07-13 14:15 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=3a52f0c5-85c5-4077-b6cd-504cc5383817@web.de \
--to=markus.elfring@web.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®