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
| ||
|
Date: Tue, 21 Jun 2016 11:35:38 +0200 From: Johannes Berg <johannes@...solutions.net> To: Pavel Machek <pavel@....cz>, João Paulo Rechi Vita <jprvita@...il.com> Cc: "David S. Miller" <davem@...emloft.net>, Darren Hart <dvhart@...radead.org>, linux-wireless <linux-wireless@...r.kernel.org>, Network Development <netdev@...r.kernel.org>, platform-driver-x86@...r.kernel.org, linux-api@...r.kernel.org, linux-doc@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, linux@...lessm.com, João Paulo Rechi Vita <jprvita@...lessm.com> Subject: Re: [RESEND PATCH 1/3] rfkill: Create "rfkill-airplane-mode" LED trigger On Mon, 2016-06-13 at 23:21 +0200, Pavel Machek wrote: > > (Actually, "::wifi" is super confusing, I'd expect that to be a led > that blinks when wifi is active.) Agree with that, yeah, that'd be confusing. > Well... "airplane" is quite confusing. I'd we use "rfkill" for > disabling radios, and I believe we should stick with that. > > But small problem might be polarity. You may need both "::rfkill" and > "::not-rfkill". I'd argue that "airplane" matches better what you're likely to find on the chassis of the system. In either case I think the suffixes should be documented, for both future kernel and application developers. johannes
Powered by blists - more mailing lists