[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTilrYYHjcMEhhrP7zjcLoo-TNczozxJSNRkDvSZy@mail.gmail.com>
Date: Wed, 9 Jun 2010 09:58:37 -0400
From: Bob Copeland <me@...copeland.com>
To: Dmytro Milinevskyy <milinevskyy@...il.com>
Cc: ath5k-devel@...ts.ath5k.org, Kalle Valo <kalle.valo@....fi>,
linux-wireless@...r.kernel.org,
GeunSik Lim <geunsik.lim@...sung.com>,
Jiri Slaby <jirislaby@...il.com>,
Greg Kroah-Hartman <gregkh@...e.de>,
"John W. Linville" <linville@...driver.com>,
Keng-Yu Lin <keng-yu.lin@...onical.com>,
netdev@...r.kernel.org, Jiri Kosina <jkosina@...e.cz>,
Shahar Or <shahar@...har-or.co.il>,
linux-kernel@...r.kernel.org, Luca Verdesca <magooz@...ug.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.
On Wed, Jun 9, 2010 at 3:31 AM, Dmytro Milinevskyy
<milinevskyy@...il.com> wrote:
> However if the leds support was enabled do not force selection of 802.11 leds layer.
I don't understand this part. What's the point of enabling software LEDs
if nothing triggers them?
Also, we can probably build hardware LEDs (hw_set_ledstate) in regardless.
It's a pure register write and doesn't require the rest of the LED machinery.
I assume you are doing this to reduce the size of the module. If so, can
you include size(1) output in the commit message?
--
Bob Copeland %% www.bobcopeland.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists