From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] h1940-leds: Fix compile issue introduced by latch-related changes
Date: Wed, 17 Nov 2010 08:55:47 +0200 [thread overview]
Message-ID: <201011170855.47991.anarsoul@gmail.com> (raw)
In-Reply-To: <4CE30FFA.7000204@fluff.org>
On Wednesday 17 November 2010 01:12:58 Ben Dooks wrote:
> it's a pitty we can't remove the driver totally and use the
> gpio leds.
Why? It's possible to use leds-gpio driver. Additional gpios (blink, etc) can
be handled via platform_gpio_blink_set callback.
Regards
Vasily
next prev parent reply other threads:[~2010-11-17 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 20:31 [PATCH 1/2] ARM: S3C2410: H1940: Adapt h1940-bluetooth to gpiolib changes Vasily Khoruzhick
2010-11-08 20:31 ` [PATCH 2/2] h1940-leds: Fix compile issue introduced by latch-related changes Vasily Khoruzhick
2010-11-15 3:55 ` Kukjin Kim
2010-11-16 23:12 ` Ben Dooks
2010-11-17 6:55 ` Vasily Khoruzhick [this message]
2010-12-06 16:43 ` Vasily Khoruzhick
2010-11-16 9:20 ` [PATCH 1/2] ARM: S3C2410: H1940: Adapt h1940-bluetooth to gpiolib changes Kukjin Kim
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=201011170855.47991.anarsoul@gmail.com \
--to=anarsoul@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).