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: <1243638870.13863.1.camel@johannes.local>
Date:	Sat, 30 May 2009 01:14:30 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Tobias Doerffel <tobias.doerffel@...il.com>
Cc:	Bob Copeland <me@...copeland.com>,
	Jiri Slaby <jirislaby@...il.com>, ath5k-devel@...ts.ath5k.org,
	mickflemm@...il.com, linux-wireless@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ath5k: added initial RFKILL support

On Sat, 2009-05-30 at 00:33 +0200, Tobias Doerffel wrote:

> > Could you try to work against v11
> > of my rfkill patch, or better even against the cfg80211 rfkill instead?
> I didn't look at both of them yet. However I think we first should try to get 
> current rfkill support into mainline as fast as possible. Improvements and 
> adaptations to reworked rfkill framework can follow.

No other comments from me -- but since the v11 of the rfkill rewrite
will certainly hit the tree before your patch (it's almost in) you
_will_ have to work against it. I'll also try to make the cfg80211
rfkill hit the tree very soon for reasons I'll explain elsewhere -- you
would be better off working against that because then your rfkill code
is very very very simple and doesn't need to do much at all.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (802 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ