From: vaibhavddit@gmail.com
To: mchehab@kernel.org
Cc: linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
rvarsha016@gmail.com, Vaibhav Kothari <vaibhavddit@gmail.com>
Subject: [PATCH] staging: media: atomisp: i2c: removed unnecessary white space before comma in memset()
Date: Tue, 28 Mar 2017 10:44:44 +0530 [thread overview]
Message-ID: <1490678084-12740-1-git-send-email-vaibhavddit@gmail.com> (raw)
In-Reply-To: <1490614949-30985-1-git-send-email-vaibhavddit@gmail.com>
gc2235.c
Removed extra space before comma in memset() as a part of
checkpatch.pl fix-up.
Signed-off-by: Vaibhav Kothari <vaibhavddit@gmail.com>
---
drivers/staging/media/atomisp/i2c/gc2235.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/atomisp/i2c/gc2235.c b/drivers/staging/media/atomisp/i2c/gc2235.c
index 9b41023..50f4317 100644
--- a/drivers/staging/media/atomisp/i2c/gc2235.c
+++ b/drivers/staging/media/atomisp/i2c/gc2235.c
@@ -55,7 +55,7 @@ static int gc2235_read_reg(struct i2c_client *client,
return -EINVAL;
}
- memset(msg, 0 , sizeof(msg));
+ memset(msg, 0, sizeof(msg));
msg[0].addr = client->addr;
msg[0].flags = 0;
--
1.9.1
next prev parent reply other threads:[~2017-03-28 5:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH 1/1] Correcting coding style errors & warnings>
2017-03-27 10:32 ` [PATCH] Fixing Coding Style Errors & Warning vaibhavddit
2017-03-27 11:37 ` [PATCH] Fixing up check-patch error & Warnings vaibhavddit
2017-03-27 11:42 ` [PATCH] staging:media:atomisp:i2c removed unnecessary white space before comma in memset() vaibhavddit
2017-03-27 13:01 ` Varsha Rao
2017-03-28 5:14 ` vaibhavddit [this message]
2017-03-28 5:23 ` [PATCH] staging: media: atomisp: i2c: " Greg KH
2017-03-29 4:41 ` vk
2017-03-28 5:32 ` vaibhavddit
2017-03-29 7:03 ` Greg KH
2017-04-02 19:43 Valerio Genovese
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=1490678084-12740-1-git-send-email-vaibhavddit@gmail.com \
--to=vaibhavddit@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rvarsha016@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;
as well as URLs for NNTP newsgroup(s).