From: "Bob Copeland" <me@bobcopeland.com>
To: Tobias Doerffel <tobias.doerffel@gmail.com>,
Jiri Slaby <jirislaby@gmail.com>
Cc: linville@tuxdriver.com, mickflemm@gmail.com,
lrodriguez@atheros.com, linux-wireless@vger.kernel.org,
ath5k-devel@venema.h4ckr.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ath5k: add support for radio LED
Date: Wed, 20 May 2009 16:29:42 -0400 [thread overview]
Message-ID: <20090520202124.M71221@bobcopeland.com> (raw)
In-Reply-To: <200905202216.43996.tobias.doerffel@gmail.com>
On Wed, 20 May 2009 22:16:42 +0200, Tobias Doerffel wrote
> If there's interest, I'll prepare a new patch which represents the
> current state.
I'm definitely interested in seeing rfkill gpio support getting in,
it's overdue. So I say repost it and we can fasttrack that. Digging
up your last patchset was already on my todo list.
As for patch 2/3 it might be a good idea to have support for
which-led-does-what encoded into the driver data anyway; other
people have asked for that and the "solution" of adding various
echos to sysfs LED trigger files is rather sad. OTOH it could
eventually be a lot of data to carry around.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-05-20 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1242850139-25438-1-git-send-email-jirislaby@gmail.com>
2009-05-20 20:08 ` [PATCH 2/3] ath5k: led, cleanup and prepare macros Jiri Slaby
2009-05-20 20:16 ` [PATCH 1/3] ath5k: add support for radio LED Tobias Doerffel
2009-05-20 20:28 ` Jiri Slaby
2009-05-20 20:29 ` Bob Copeland [this message]
2009-05-20 20:33 ` Tobias Doerffel
2009-05-20 20:41 ` [ath5k-devel] " Bob Copeland
2009-05-22 12:35 ` Bob Copeland
2009-05-25 23:24 ` [PATCH] ath5k: added initial RFKILL support Tobias Doerffel
2009-05-25 23:24 ` Tobias Doerffel
2009-05-25 23:32 ` Johannes Berg
2009-05-25 23:32 ` Johannes Berg
2009-05-29 22:33 ` Tobias Doerffel
2009-05-29 22:33 ` Tobias Doerffel
2009-05-29 23:14 ` Johannes Berg
2009-05-29 23:14 ` Johannes Berg
2009-05-30 15:26 ` [ath5k-devel] " Alan Jenkins
2009-05-30 15:26 ` Alan Jenkins
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=20090520202124.M71221@bobcopeland.com \
--to=me@bobcopeland.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lrodriguez@atheros.com \
--cc=mickflemm@gmail.com \
--cc=tobias.doerffel@gmail.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.