From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Maxim Levitsky <maximlevitsky@gmail.com>,
kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 3/9] memstick: Delete unwanted spaces behind three function parameters
Date: Sat, 7 Jan 2017 20:55:23 +0100 [thread overview]
Message-ID: <3e11edb7-519f-4cde-f22f-3c6bbdda536c@users.sourceforge.net> (raw)
In-Reply-To: <64dfa775-4e4a-bdb0-7b55-41f43ccdf11a@users.sourceforge.net>
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Sat, 7 Jan 2017 18:54:25 +0100
The script "checkpatch.pl" pointed information out like the following.
ERROR: space prohibited before that ',' (ctx:WxW)
Thus fix the affected source code places.
Signed-off-by: Markus Elfring <elfring@users.sourceforge.net>
---
drivers/memstick/core/ms_block.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/memstick/core/ms_block.c b/drivers/memstick/core/ms_block.c
index ec17885a5956..526e671a3435 100644
--- a/drivers/memstick/core/ms_block.c
+++ b/drivers/memstick/core/ms_block.c
@@ -194,7 +194,8 @@ static void msb_mark_block_unused(struct msb_data *msb, int pba)
int zone = msb_get_zone_from_pba(pba);
if (!test_bit(pba, msb->used_blocks_bitmap)) {
- pr_err("BUG: attempt to mark already unused pba %d as unused" , pba);
+ pr_err("BUG: attempt to mark already unused pba %d as unused",
+ pba);
msb->read_only = true;
return;
}
@@ -1551,7 +1552,7 @@ static int msb_cache_flush(struct msb_data *msb)
dbg_verbose("Flushing the write cache of pba %d (LBA %d)",
pba, msb->cache_block_lba);
- sg_init_one(&sg, msb->cache , msb->block_size);
+ sg_init_one(&sg, msb->cache, msb->block_size);
/* Read all missing pages in cache */
for (page = 0; page < msb->pages_in_block; page++) {
@@ -1597,7 +1598,9 @@ static int msb_cache_flush(struct msb_data *msb)
dbg("marking page %d as containing damaged data",
page);
msb_set_overwrite_flag(msb,
- pba , page, 0xFF & ~MEMSTICK_OV_PG_NORMAL);
+ pba,
+ page,
+ 0xFF & ~MEMSTICK_OV_PG_NORMAL);
}
}
--
2.11.0
next prev parent reply other threads:[~2017-01-07 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 19:50 [PATCH 0/9] memstick: Fine-tuning for some function implementations SF Markus Elfring
2017-01-07 19:53 ` [PATCH 1/9] memstick: Split a condition check in msb_ftl_initialize() SF Markus Elfring
2017-01-07 19:54 ` [PATCH 2/9] memstick: Use kmalloc_array() " SF Markus Elfring
2017-01-07 19:55 ` SF Markus Elfring [this message]
2017-01-07 19:56 ` [PATCH 4/9] memstick: Improve two size determinations in msb_resume() SF Markus Elfring
2017-01-07 19:57 ` [PATCH 5/9] memstick: Delete an unnecessary variable initialisation " SF Markus Elfring
2017-01-07 19:58 ` [PATCH 6/9] memstick: Improve a size determination in msb_probe() SF Markus Elfring
2017-01-07 19:59 ` [PATCH 7/9] memstick: Improve another size determination in msb_read_boot_blocks() Markus Elfring
2017-01-07 20:01 ` SF Markus Elfring
2017-01-07 20:03 ` [PATCH 8/9] memstick: Delete an unnecessary variable initialisation " SF Markus Elfring
2017-01-07 20:04 ` [PATCH 9/9] memstick: Delete an unnecessary check in msb_update_block() 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=3e11edb7-519f-4cde-f22f-3c6bbdda536c@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
/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®