linux-kernel - Re: [PATCH 1/3] ath5k: add support for radio LED

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090520202124.M71221@bobcopeland.com>
Date:	Wed, 20 May 2009 16:29:42 -0400
From:	"Bob Copeland" <me@...copeland.com>
To:	Tobias Doerffel <tobias.doerffel@...il.com>,
	Jiri Slaby <jirislaby@...il.com>
Cc:	linville@...driver.com, mickflemm@...il.com,
	lrodriguez@...eros.com, linux-wireless@...r.kernel.org,
	ath5k-devel@...ema.h4ckr.net, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] ath5k: add support for radio LED

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/