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 3/3] block-aoe: Add spaces for better code readability
Date: Mon, 8 May 2017 09:58:53 +0200 [thread overview]
Message-ID: <4068e22e-3d11-0d57-eedf-8eb696224cfb@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 09:35:25 +0200
The script "checkpatch.pl" pointed information out like the following.
CHECK: spaces preferred around that '-' (ctx:VxV)
Thus fix the affected source code place.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
drivers/block/aoe/aoeblk.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/block/aoe/aoeblk.c b/drivers/block/aoe/aoeblk.c
index a52555984e73..66adb2fb66d3 100644
--- a/drivers/block/aoe/aoeblk.c
+++ b/drivers/block/aoe/aoeblk.c
@@ -87,10 +87,10 @@ static ssize_t aoedisk_show_netif(struct device *dev,
if (!*nd)
return snprintf(page, PAGE_SIZE, "none\n");
for (p = page; nd < ne; nd++)
- p += snprintf(p, PAGE_SIZE - (p-page), "%s%s",
- p == page ? "" : ",", (*nd)->name);
- p += snprintf(p, PAGE_SIZE - (p-page), "\n");
- return p-page;
+ p += snprintf(p, PAGE_SIZE - (p - page), "%s%s",
+ p == page ? "" : ",", (*nd)->name);
+ p += snprintf(p, PAGE_SIZE - (p - page), "\n");
+ return p - page;
}
/* firmware version */
static ssize_t aoedisk_show_fwver(struct device *dev,
--
2.12.2
prev parent reply other threads:[~2017-05-08 7:59 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 ` [PATCH 1/3] block-aoe: Use seq_putc() in aoedisk_debugfs_show() SF Markus Elfring
2017-05-08 7:57 ` [PATCH 2/3] block-aoe: Adjust eight checks for null pointers SF Markus Elfring
2017-05-08 7:58 ` SF 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=4068e22e-3d11-0d57-eedf-8eb696224cfb@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®