mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 1/2] pwm: Simplify data output in pwm_dbg_show()
Date: Fri, 5 Jun 2026 16:23:53 +0200	[thread overview]
Message-ID: <b854002b-08fd-476f-b2e3-631f1354623b@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 15:57:58 +0200

Move the specification for a line break from a seq_puts() call
to a seq_printf() call.

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, 1 insertion(+), 3 deletions(-)

diff --git a/drivers/pwm/core.c b/drivers/pwm/core.c
index be4885da85b6..1138b3ffbc12 100644
--- a/drivers/pwm/core.c
+++ b/drivers/pwm/core.c
@@ -2647,9 +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_printf(s, "  requested configuration: %3sabled, %llu/%llu ns, %s polarity",
+		seq_printf(s, "\n  requested configuration: %3sabled, %llu/%llu ns, %s polarity",
 			   state.enabled ? "en" : "dis", state.duty_cycle, state.period,
 			   state.polarity ? "inverse" : "normal");
 		if (state.usage_power)
-- 
2.54.0


  reply	other threads:[~2026-06-05 14:24 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 " Markus Elfring
2026-06-05 14:23 ` Markus Elfring [this message]
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   ` [PATCH] pwm: Use another seq_putc() call " Markus Elfring

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=b854002b-08fd-476f-b2e3-631f1354623b@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