From: Sheetal Tigadoli <sheetal.tigadoli@gmail.com>
To: chris@printf.net
Cc: joe@perches.com, linux-mmc@vger.kernel.org, ben@decadent.org.uk,
kuninori.morimoto.gx@renesas.com, ulf.hansson@linaro.org,
linux-kernel@vger.kernel.org,
Sheetal Tigadoli <sheetal.tigadoli@gmail.com>
Subject: [PATCH 4/5] drivers: mmc: card: Fixed ERROR that open brace should be on the previous line
Date: Mon, 2 Feb 2015 01:37:01 +0530 [thread overview]
Message-ID: <1422821222-24079-5-git-send-email-sheetal.tigadoli@gmail.com> (raw)
In-Reply-To: <1422821222-24079-4-git-send-email-sheetal.tigadoli@gmail.com>
The Patch fixes the below coding style error found using checkpatch.pl script
drivers/mmc/card/block.c:2362: ERROR: that open brace { should be on the previous line
Signed-off-by: Sheetal Tigadoli <sheetal.tigadoli@gmail.com>
---
drivers/mmc/card/block.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c
index 2394d0b..fe47297 100644
--- a/drivers/mmc/card/block.c
+++ b/drivers/mmc/card/block.c
@@ -2358,8 +2358,7 @@ force_ro_fail:
#define CID_MANFID_MICRON 0x13
#define CID_MANFID_SAMSUNG 0x15
-static const struct mmc_fixup blk_fixups[] =
-{
+static const struct mmc_fixup blk_fixups[] = {
MMC_FIXUP("SEM02G", CID_MANFID_SANDISK, 0x100, add_quirk,
MMC_QUIRK_INAND_CMD38),
MMC_FIXUP("SEM04G", CID_MANFID_SANDISK, 0x100, add_quirk,
--
1.7.9.5
next prev parent reply other threads:[~2015-02-01 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 20:06 [PATCH 0/5] drivers; mmc: card: Sheetal Tigadoli
2015-02-01 20:06 ` [PATCH 1/5] drivers: mmc: card: Fix replaces simple_strtoul func call with kstrtoul Sheetal Tigadoli
2015-02-01 20:06 ` [PATCH 2/5] drivers: mmc: card: Fixes Missing blank line after variable initialization, coding style warning Sheetal Tigadoli
2015-02-01 20:07 ` [PATCH 3/5] drivers: mmc: card: Fixes WARNING braces are not necessary for single statement Sheetal Tigadoli
2015-02-01 20:07 ` Sheetal Tigadoli [this message]
2015-02-01 20:07 ` [PATCH 5/5] drivers: mmc: card: Fixed warning line over 80 characters in file block Sheetal Tigadoli
2015-02-01 20:20 ` [PATCH 2/5] drivers: mmc: card: Fixes Missing blank line after variable initialization, coding style warning Joe Perches
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=1422821222-24079-5-git-send-email-sheetal.tigadoli@gmail.com \
--to=sheetal.tigadoli@gmail.com \
--cc=ben@decadent.org.uk \
--cc=chris@printf.net \
--cc=joe@perches.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.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