From: Markus Elfring <Markus.Elfring@web.de>
To: linux-pwm@vger.kernel.org, "Uwe Kleine-König" <ukleinek@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 2/2] pwm: Use seq_putc() calls in pwm_dbg_show()
Date: Fri, 5 Jun 2026 16:25:20 +0200 [thread overview]
Message-ID: <5cc95f1d-a9f4-4ba4-8411-56cfb16d996a@web.de> (raw)
In-Reply-To: <3e9f9238-a0e4-4a29-8a5b-27e4a5a0e1e2@web.de>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Fri, 5 Jun 2026 16:12:53 +0200
Single characters should occasionally 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 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
index 1138b3ffbc12..41b02a4a94f3 100644
--- a/drivers/pwm/core.c
+++ b/drivers/pwm/core.c
@@ -2652,7 +2652,7 @@ static void pwm_dbg_show(struct pwm_chip *chip, struct seq_file *s)
state.polarity ? "inverse" : "normal");
if (state.usage_power)
seq_puts(s, ", usage_power");
- seq_puts(s, "\n");
+ seq_putc(s, '\n');
if (pwmchip_supports_waveform(chip)) {
struct pwm_waveform wf;
@@ -2675,7 +2675,7 @@ static void pwm_dbg_show(struct pwm_chip *chip, struct seq_file *s)
seq_printf(s, " actual configuration: read out error: %pe", ERR_PTR(err));
}
- seq_puts(s, "\n");
+ seq_putc(s, '\n');
}
}
--
2.54.0
next prev parent reply other threads:[~2026-06-05 14:25 UTC|newest]
Thread overview: 6+ 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 ` Markus Elfring [this message]
2026-07-16 7:45 ` [PATCH 0/2] pwm: More efficient " Uwe Kleine-König
2026-07-17 9:40 ` [PATCH] pwm: Use another seq_putc() call " Markus Elfring
2026-07-19 17:10 ` Uwe Kleine-König
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=5cc95f1d-a9f4-4ba4-8411-56cfb16d996a@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
all inboxes | Powered by JetHome®