mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: kernel-janitors@vger.kernel.org,
	"Gregory Clement" <gregory.clement@free-electrons.com>,
	"Jan Lübbe" <jlu@pengutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/2] mvebu-mbus: Use seq_putc() in mvebu_devs_debug_show()
Date: Fri, 12 Jan 2018 17:58:42 +0100	[thread overview]
Message-ID: <8dae6f05-2403-42d3-8728-96d69e4a965b@users.sourceforge.net> (raw)
In-Reply-To: <4796228f-fa7f-24db-0049-2d2b9041c5b0@users.sourceforge.net>

From: Markus Elfring <elfring@users.sourceforge.net>
Date: Fri, 12 Jan 2018 17:12:14 +0100

A single character (line break) should be put into a sequence.
Thus use the corresponding function "seq_putc".

This issue was detected by using the Coccinelle software.

Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
 drivers/bus/mvebu-mbus.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/bus/mvebu-mbus.c b/drivers/bus/mvebu-mbus.c
index 70db4d5638a6..5844901aea0b 100644
--- a/drivers/bus/mvebu-mbus.c
+++ b/drivers/bus/mvebu-mbus.c
@@ -514,7 +514,7 @@ static int mvebu_devs_debug_show(struct seq_file *seq, void *v)
 			seq_printf(seq, " (remap %016llx)\n",
 				   (unsigned long long)wremap);
 		} else
-			seq_printf(seq, "\n");
+			seq_putc(seq, '\n');
 	}
 
 	return 0;
-- 
2.15.1

  reply	other threads:[~2018-01-12 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 16:57 [PATCH 0/2] mvebu-mbus: Adjustments for mvebu_devs_debug_show() SF Markus Elfring
2018-01-12 16:58 ` SF Markus Elfring [this message]
2018-01-12 17:00 ` [PATCH 2/2] mvebu-mbus: Fix a typo in five comment lines SF 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=8dae6f05-2403-42d3-8728-96d69e4a965b@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --cc=gregory.clement@free-electrons.com \
    --cc=jlu@pengutronix.de \
    --cc=kernel-janitors@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

Powered by JetHome