From: SF Markus Elfring <elfring@users.sourceforge.net>
To: kernel-janitors@vger.kernel.org, "Ed L. Cashin" <ed.cashin@acm.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/3] block-aoe: Use seq_putc() in aoedisk_debugfs_show()
Date: Mon, 8 May 2017 09:56:44 +0200 [thread overview]
Message-ID: <58b532fc-14c5-6e87-75d0-d78703b289dc@users.sourceforge.net> (raw)
In-Reply-To: <705a2cf5-90fe-ec8a-95f9-a27bccbc3f3f@users.sourceforge.net>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Mon, 8 May 2017 08:51:28 +0200
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/block/aoe/aoeblk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/aoe/aoeblk.c b/drivers/block/aoe/aoeblk.c
index 027b876370bc..cfcf21ec123d 100644
--- a/drivers/block/aoe/aoeblk.c
+++ b/drivers/block/aoe/aoeblk.c
@@ -147,7 +147,7 @@ static int aoedisk_debugfs_show(struct seq_file *s, void *ignored)
seq_printf(s, "%c%s", c, ifp->nd->name);
c = ',';
}
- seq_puts(s, "\n");
+ seq_putc(s, '\n');
}
spin_unlock_irqrestore(&d->lock, flags);
--
2.12.2
next prev parent reply other threads:[~2017-05-08 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 7:55 [PATCH 0/3] block-AoE: Fine-tuning for six function implementations SF Markus Elfring
2017-05-08 7:56 ` SF Markus Elfring [this message]
2017-05-08 7:57 ` [PATCH 2/3] block-aoe: Adjust eight checks for null pointers SF Markus Elfring
2017-05-08 7:58 ` [PATCH 3/3] block-aoe: Add spaces for better code readability 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=58b532fc-14c5-6e87-75d0-d78703b289dc@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=ed.cashin@acm.org \
--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
all inboxes | Powered by JetHome®