From: akpm@linux-foundation.org
To: cascardo@holoscopio.com, rpurdie@rpsys.net,
srcvale@holoscopio.com, mm-commits@vger.kernel.org
Subject: [merged] leds-fix-coding-style-in-worker-thread-code-for-ledtrig-gpio.patch removed from -mm tree
Date: Tue, 08 Sep 2009 14:26:19 -0700 [thread overview]
Message-ID: <200909082126.n88LQJOU006730@imap1.linux-foundation.org> (raw)
The patch titled
leds: fix coding style in worker thread code for ledtrig-gpio.
has been removed from the -mm tree. Its filename was
leds-fix-coding-style-in-worker-thread-code-for-ledtrig-gpio.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: leds: fix coding style in worker thread code for ledtrig-gpio.
From: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Signed-off-by: Samuel R. C. Vale <srcvale@holoscopio.com>
Cc: Richard Purdie <rpurdie@rpsys.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/leds/ledtrig-gpio.c | 30 +++++++++++++++---------------
1 file changed, 15 insertions(+), 15 deletions(-)
diff -puN drivers/leds/ledtrig-gpio.c~leds-fix-coding-style-in-worker-thread-code-for-ledtrig-gpio drivers/leds/ledtrig-gpio.c
--- a/drivers/leds/ledtrig-gpio.c~leds-fix-coding-style-in-worker-thread-code-for-ledtrig-gpio
+++ a/drivers/leds/ledtrig-gpio.c
@@ -44,22 +44,22 @@ static void gpio_trig_work(struct work_s
struct gpio_trig_data, work);
int tmp;
- if (!gpio_data->gpio)
- return;
+ if (!gpio_data->gpio)
+ return;
- tmp = gpio_get_value(gpio_data->gpio);
- if (gpio_data->inverted)
- tmp = !tmp;
-
- if (tmp) {
- if (gpio_data->desired_brightness)
- led_set_brightness(gpio_data->led,
- gpio_data->desired_brightness);
- else
- led_set_brightness(gpio_data->led, LED_FULL);
- } else {
- led_set_brightness(gpio_data->led, LED_OFF);
- }
+ tmp = gpio_get_value(gpio_data->gpio);
+ if (gpio_data->inverted)
+ tmp = !tmp;
+
+ if (tmp) {
+ if (gpio_data->desired_brightness)
+ led_set_brightness(gpio_data->led,
+ gpio_data->desired_brightness);
+ else
+ led_set_brightness(gpio_data->led, LED_FULL);
+ } else {
+ led_set_brightness(gpio_data->led, LED_OFF);
+ }
}
static ssize_t gpio_trig_brightness_show(struct device *dev,
_
Patches currently in -mm which might be from cascardo@holoscopio.com are
linux-next.patch
reply other threads:[~2009-09-08 21:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200909082126.n88LQJOU006730@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cascardo@holoscopio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=srcvale@holoscopio.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.