From: Jingoo Han <jg1.han@samsung.com>
To: 'Bryan Wu' <cooloney@gmail.com>
Cc: linux-leds@vger.kernel.org,
"'Richard Purdie'" <rpurdie@rpsys.net>,
"'Jingoo Han'" <jg1.han@samsung.com>,
"'Jan-Simon Möller'" <dl9pf@gmx.de>
Subject: [PATCH 5/5] leds: blinkm: remove unnecessary spaces
Date: Wed, 26 Feb 2014 14:16:11 +0900 [thread overview]
Message-ID: <000f01cf32b1$dd460ef0$97d22cd0$%han@samsung.com> (raw)
In-Reply-To: <000b01cf32b0$eb62fe40$c228fac0$%han@samsung.com>
Remove unnecessary space in order to fix the following
checkpatch issues.
WARNING: space prohibited before semicolon
Signed-off-by: Jingoo Han <jg1.han@samsung.com>
---
drivers/leds/leds-blinkm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/leds/leds-blinkm.c b/drivers/leds/leds-blinkm.c
index 0c50860..d0452b0 100644
--- a/drivers/leds/leds-blinkm.c
+++ b/drivers/leds/leds-blinkm.c
@@ -443,7 +443,7 @@ static void led_work(struct work_struct *work)
{
int ret;
struct blinkm_led *led;
- struct blinkm_data *data ;
+ struct blinkm_data *data;
struct blinkm_work *blm_work = work_to_blmwork(work);
led = blm_work->blinkm_led;
--
1.7.10.4
next prev parent reply other threads:[~2014-02-26 5:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 5:09 [PATCH 1/5] leds: leds-ss4200: fix incorrect placement of __initdata marker Jingoo Han
2014-02-26 5:10 ` [PATCH 2/5] leds: leds-ss4200: remove DEFINE_PCI_DEVICE_TABLE macro Jingoo Han
2014-02-27 18:01 ` Bryan Wu
2014-02-26 5:11 ` [PATCH 3/5] leds: lp5562: remove unnecessary parentheses Jingoo Han
2014-02-27 18:03 ` Bryan Wu
2014-02-26 5:14 ` [PATCH 4/5] leds: clevo-mail: fix incorrect placement of __initdata marker Jingoo Han
2014-02-26 8:30 ` Uwe Kleine-König
2014-02-27 18:16 ` Bryan Wu
2014-02-26 5:16 ` Jingoo Han [this message]
2014-02-26 6:25 ` [PATCH 5/5] leds: blinkm: remove unnecessary spaces Jan-Simon Möller
2014-02-27 18:22 ` Bryan Wu
2014-02-27 18:00 ` [PATCH 1/5] leds: leds-ss4200: fix incorrect placement of __initdata marker Bryan Wu
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='000f01cf32b1$dd460ef0$97d22cd0$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=cooloney@gmail.com \
--cc=dl9pf@gmx.de \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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).