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
| ||
|
Message-ID: <87d0cugbe5.fsf@toke.dk> Date: Wed, 11 Dec 2019 15:55:14 +0100 From: Toke Høiland-Jørgensen <toke@...hat.com> To: Johannes Berg <johannes@...solutions.net>, Jens Axboe <axboe@...nel.dk>, Emmanuel Grumbach <emmanuel.grumbach@...el.com>, Luca Coelho <luciano.coelho@...el.com>, "Jason A. Donenfeld" <Jason@...c4.com>, Steve French <smfrench@...il.com> Cc: "linux-wireless\@vger.kernel.org" <linux-wireless@...r.kernel.org>, Networking <netdev@...r.kernel.org> Subject: Re: iwlwifi warnings in 5.5-rc1 Johannes Berg <johannes@...solutions.net> writes: > On Wed, 2019-12-11 at 15:09 +0100, Toke Høiland-Jørgensen wrote: >> >> If we're doing this on a per-driver basis, let's make it a proper >> NL80211_EXT_FEATURE and expose it to userspace; that way users can at >> least discover if it's supported on their device. I can send a patch >> adding that... > > Sure. Just didn't get to that yet, but if you want to send a patch > that's very welcome. I have to run out now, will be back in the evening > at most. Patch here (for those not following linux-wireless): https://patchwork.kernel.org/project/linux-wireless/list/?series=215107 >> Maybe we should untangle this from airtime_flags completely, since if we >> just use the flags people could conceivably end up disabling it by >> mistake, couldn't they? > > Yes, that sounds like a good plan, now I was wondering why it's there > anyway. Convenience, I think :) -Toke
Powered by blists - more mailing lists