From: Jingoo Han <jg1.han@samsung.com>
To: "'Andrew Morton'" <akpm@linux-foundation.org>,
"'LKML'" <linux-kernel@vger.kernel.org>
Cc: "'Richard Purdie'" <rpurdie@rpsys.net>,
"'Jingoo Han'" <jg1.han@samsung.com>
Subject: [PATCH 13/17] backlight: pcf50633: fix checkpatch warning
Date: Tue, 16 Oct 2012 16:32:28 +0900 [thread overview]
Message-ID: <007e01cdab70$65049b60$2f0dd220$%han@samsung.com> (raw)
In-Reply-To: <007101cdab6f$6c8bc030$45a34090$%han@samsung.com>
This patch fixes the checkpatch warning as below:
WARNING: please, no spaces at the start of a line
Also, long comments are fixed for the preferred style.
Signed-off-by: Jingoo Han <jg1.han@samsung.com>
Cc: Richard Purdie <rpurdie@rpsys.net>
---
drivers/video/backlight/pcf50633-backlight.c | 8 +++++---
1 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/video/backlight/pcf50633-backlight.c b/drivers/video/backlight/pcf50633-backlight.c
index c092159..930fc2a 100644
--- a/drivers/video/backlight/pcf50633-backlight.c
+++ b/drivers/video/backlight/pcf50633-backlight.c
@@ -52,7 +52,7 @@ int pcf50633_bl_set_brightness_limit(struct pcf50633 *pcf, unsigned int limit)
pcf_bl->brightness_limit = limit & 0x3f;
backlight_update_status(pcf_bl->bl);
- return 0;
+ return 0;
}
static int pcf50633_bl_update_status(struct backlight_device *bl)
@@ -136,8 +136,10 @@ static int __devinit pcf50633_bl_probe(struct platform_device *pdev)
pcf50633_reg_write(pcf_bl->pcf, PCF50633_REG_LEDDIM, pdata->ramp_time);
- /* Should be different from bl_props.brightness, so we do not exit
- * update_status early the first time it's called */
+ /*
+ * Should be different from bl_props.brightness, so we do not exit
+ * update_status early the first time it's called
+ */
pcf_bl->brightness = pcf_bl->bl->props.brightness + 1;
backlight_update_status(pcf_bl->bl);
--
1.7.1
next prev parent reply other threads:[~2012-10-16 7:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 7:25 [PATCH 01/17] backlight: 88pm860x_bl: fix checkpatch warning Jingoo Han
2012-10-16 7:26 ` [PATCH 02/17] backlight: atmel-pwm-bl: " Jingoo Han
2012-10-16 7:27 ` [PATCH 03/17] backlight: corgi_lcd: fix checkpatch error and warning Jingoo Han
2012-10-16 7:27 ` [PATCH 04/17] backlight: da903x_bl: fix checkpatch warning Jingoo Han
2012-10-16 7:28 ` [PATCH 05/17] backlight: generic_bl: " Jingoo Han
2012-10-16 7:28 ` [PATCH 06/17] backlight: hp680_bl: fix checkpatch error and warning Jingoo Han
2012-10-16 7:29 ` [PATCH 07/17] backlight: ili9320: " Jingoo Han
2012-10-16 7:30 ` [PATCH 08/17] backlight: jornada720: " Jingoo Han
2012-10-16 15:46 ` Kristoffer Eriksson
2012-10-16 7:30 ` [PATCH 09/17] backlight: l4f00242t03: fix checkpatch warning Jingoo Han
2012-10-16 7:30 ` [PATCH 10/17] backlight: lm3630: " Jingoo Han
2012-10-16 7:31 ` [PATCH 11/17] backlight: locomolcd: fix checkpatch error and warning Jingoo Han
2012-10-16 7:31 ` [PATCH 12/17] backlight: omap1: fix checkpatch warning Jingoo Han
2012-10-16 7:32 ` Jingoo Han [this message]
2012-10-16 7:32 ` [PATCH 14/17] backlight: platform_lcd: fix checkpatch error Jingoo Han
2012-10-16 7:33 ` [PATCH 15/17] backlight: tdo24m: fix checkpatch warning Jingoo Han
2012-10-16 7:33 ` [PATCH 16/17] backlight: tosa: fix checkpatch error and warning Jingoo Han
2012-10-16 7:34 ` [PATCH 17/17] backlight: vgg2432a4: fix checkpatch warning Jingoo Han
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='007e01cdab70$65049b60$2f0dd220$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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