From: Bob Copeland <me@bobcopeland.com>
To: Dmytro Milinevskyy <milinevskyy@gmail.com>
Cc: Kalle Valo <kalle.valo@iki.fi>,
GeunSik Lim <geunsik.lim@samsung.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Jiri Slaby <jirislaby@gmail.com>,
netdev@vger.kernel.org, ath5k-devel@venema.h4ckr.net,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Keng-Yu Lin <keng-yu.lin@canonical.com>,
Jiri Kosina <jkosina@suse.cz>, Shahar Or <shahar@shahar-or.co.il>,
linux-kernel@vger.kernel.org, Luca Verdesca <magooz@salug.it>
Subject: Re: [ath5k-devel] [PATCH] [ath5k][leds] Ability to disable leds support. If leds support enabled do not force mac802.11 leds layer selection.
Date: Fri, 11 Jun 2010 13:07:42 -0400 [thread overview]
Message-ID: <AANLkTimUW58T19GOkRk3oCC9huLDQLgLj4W3RjiQ9n53@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimXqdkQxv_Y1JaleTTWNsDIQHQaPn8HR7efOupb@mail.gmail.com>
On Wed, Jun 9, 2010 at 10:43 AM, Dmytro Milinevskyy
<milinevskyy@gmail.com> wrote:
> Hi, Bob.
>
> For instance I don't use 802.11 leds layer and trigger leds from
> userspace according to my purposes.
FWIW you can disable mac80211 triggers from userspace as well.
But, I guess hooking up null triggers will work too.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2010-06-11 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 7:31 [PATCH] [ath5k][leds] Ability to disable leds support. If leds support enabled do not force mac802.11 leds layer selection Dmytro Milinevskyy
2010-06-09 13:58 ` [ath5k-devel] " Bob Copeland
2010-06-09 14:43 ` Dmytro Milinevskyy
2010-06-11 17:07 ` Bob Copeland [this message]
2010-06-11 19:52 ` Dmytro Milinevskyy
2010-06-11 20:09 ` Johannes Berg
2010-06-11 20:26 ` Dmytro Milinevskyy
2010-06-11 20:29 ` Johannes Berg
2010-06-12 2:02 ` Dmytro Milinevskyy
[not found] <4bea1f81.09b6660a.746e.1c12@mx.google.com>
2010-05-12 15:48 ` Pavel Roskin
2010-05-13 7:36 ` Dmytro Milinevskyy
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=AANLkTimUW58T19GOkRk3oCC9huLDQLgLj4W3RjiQ9n53@mail.gmail.com \
--to=me@bobcopeland.com \
--cc=ath5k-devel@venema.h4ckr.net \
--cc=geunsik.lim@samsung.com \
--cc=gregkh@suse.de \
--cc=jirislaby@gmail.com \
--cc=jkosina@suse.cz \
--cc=kalle.valo@iki.fi \
--cc=keng-yu.lin@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=magooz@salug.it \
--cc=milinevskyy@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shahar@shahar-or.co.il \
/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).