From: Mohammad Jamal <md.jamalmohiuddin@gmail.com>
To: dwmw2@infradead.org
Cc: computersforpeace@gmail.com, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org,
Mohammad Jamal <md.jamalmohiuddin@gmail.com>
Subject: [PATCH] mtd: ssfdc: Fix space before ( coding style
Date: Fri, 19 Dec 2014 20:00:13 +0530 [thread overview]
Message-ID: <1418999413-29428-1-git-send-email-md.jamalmohiuddin@gmail.com> (raw)
Patch solves the space before ( coding style issue of ssfdc.c
Signed-off-by: Mohammad Jamal <md.jamalmohiuddin@gmail.com>
---
drivers/mtd/ssfdc.c | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/mtd/ssfdc.c b/drivers/mtd/ssfdc.c
index daf82ba..d4a922c 100644
--- a/drivers/mtd/ssfdc.c
+++ b/drivers/mtd/ssfdc.c
@@ -42,8 +42,8 @@ struct ssfdcr_record {
#define MAX_LOGIC_BLK_PER_ZONE 1000
#define MAX_PHYS_BLK_PER_ZONE 1024
-#define KiB(x) ( (x) * 1024L )
-#define MiB(x) ( KiB(x) * 1024L )
+#define KiB(x) ((x) * 1024L)
+#define MiB(x) (KiB(x) * 1024L)
/** CHS Table
1MiB 2MiB 4MiB 8MiB 16MiB 32MiB 64MiB 128MiB
@@ -63,13 +63,13 @@ typedef struct {
/* Must be ordered by size */
static const chs_entry_t chs_table[] = {
- { MiB( 1), 125, 4, 4 },
- { MiB( 2), 125, 4, 8 },
- { MiB( 4), 250, 4, 8 },
- { MiB( 8), 250, 4, 16 },
- { MiB( 16), 500, 4, 16 },
- { MiB( 32), 500, 8, 16 },
- { MiB( 64), 500, 8, 32 },
+ { MiB(1), 125, 4, 4 },
+ { MiB(2), 125, 4, 8 },
+ { MiB(4), 250, 4, 8 },
+ { MiB(8), 250, 4, 16 },
+ { MiB(16), 500, 4, 16 },
+ { MiB(32), 500, 8, 16 },
+ { MiB(64), 500, 8, 32 },
{ MiB(128), 500, 16, 32 },
{ 0 },
};
--
1.7.9.5
next reply other threads:[~2014-12-19 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 14:30 Mohammad Jamal [this message]
2014-12-19 15:20 ` [PATCH] mtd: ssfdc: Fix space before ( coding style Jeremiah Mahler
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=1418999413-29428-1-git-send-email-md.jamalmohiuddin@gmail.com \
--to=md.jamalmohiuddin@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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