From: Markus Elfring <Markus.Elfring@web.de>
To: "Uwe Kleine-König" <ukleinek@kernel.org>, linux-pwm@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH] pwm: Use another seq_putc() call in pwm_dbg_show()
Date: Fri, 17 Jul 2026 11:40:45 +0200 [thread overview]
Message-ID: <03062fdb-cc4f-47c7-a007-4ac67ded6377@web.de> (raw)
In-Reply-To: <aliLpfmKkkwlZhzF@monoceros>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Fri, 17 Jul 2026 11:33:55 +0200
A single line break should be put into a sequence.
Thus use the corresponding function “seq_putc”.
The source code was transformed by using the Coccinelle software.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
drivers/pwm/core.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
index fa0f8f1f6ed0..c2d77082c549 100644
--- a/drivers/pwm/core.c
+++ b/drivers/pwm/core.c
@@ -2647,8 +2647,7 @@ static void pwm_dbg_show(struct pwm_chip *chip, struct seq_file *s)
if (test_bit(PWMF_REQUESTED, &pwm->flags))
seq_puts(s, " requested");
- seq_puts(s, "\n");
-
+ seq_putc(s, '\n');
seq_printf(s, " requested configuration: %3sabled, %llu/%llu ns, %s polarity",
state.enabled ? "en" : "dis", state.duty_cycle, state.period,
state.polarity ? "inverse" : "normal");
--
2.55.0
prev parent reply other threads:[~2026-07-17 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 14:22 [PATCH 0/2] pwm: More efficient data output " Markus Elfring
2026-06-05 14:23 ` [PATCH 1/2] pwm: Simplify " Markus Elfring
2026-06-05 14:25 ` [PATCH 2/2] pwm: Use seq_putc() calls " Markus Elfring
2026-07-16 7:45 ` [PATCH 0/2] pwm: More efficient data output " Uwe Kleine-König
2026-07-17 9:40 ` Markus Elfring [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=03062fdb-cc4f-47c7-a007-4ac67ded6377@web.de \
--to=markus.elfring@web.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=ukleinek@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