From: anarsoul@gmail.com (Vasily Khoruzhick)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] leds/h1940: Use gpiolib for latch access / fix build failure
Date: Thu, 6 Jan 2011 18:03:25 +0200 [thread overview]
Message-ID: <201101061803.26194.anarsoul@gmail.com> (raw)
In-Reply-To: <20110104153725.2f3fede2.akpm@linux-foundation.org>
On Wednesday 05 January 2011 01:37:25 Andrew Morton wrote:
> So which patch to use?
>
> I queued Peter's patch because it's simpler. I queued it for
> 2.6.38-rc1, taged for backporting into 2.6.37.x, so we have a bit of
> time to think about it.
Anyway, it's time to drop leds-h1940 driver, I'll submit patch to support
H1940 leds via generic leds-gpio driver tonight.
Regards
Vasily
prev parent reply other threads:[~2011-01-06 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 22:04 [PATCH] leds/h1940: Use gpiolib for latch access / fix build failure Peter Huewe
2010-12-09 22:16 ` Vasily Khoruzhick
2011-01-04 23:37 ` Andrew Morton
2011-01-05 7:08 ` Vasily Khoruzhick
2011-01-06 16:03 ` Vasily Khoruzhick [this message]
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=201101061803.26194.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).