netdev - Re: Please pull 'z1211' branch of wireless-2.6

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]

Date:	Wed, 19 Sep 2007 15:32:56 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dsd@...too.org
Cc:	linville@...driver.com, jeff@...zik.org, netdev@...r.kernel.org,
	linux-wireless@...r.kernel.org, kune@...ne-taler.de
Subject: Re: Please pull 'z1211' branch of wireless-2.6

From: Daniel Drake <dsd@...too.org>
Date: Wed, 19 Sep 2007 23:27:09 +0100

> zd1211rw-mac80211 does not currently add anything to the user experience 
> over the existing driver, other than automatic rate adaption which is 
> nice but hasn't proven itself to be of much importance given that the 
> existing driver has lots of happy users and has never done it.

Ok.

> Also, this merge has been proposed in a form other than what me and 
> Ulrich were envisioning (at least from earlier discussions). We want to 
> convert drivers/net/wireless/zd1211rw to mac80211 directly. This would 
> also avoid a rename and I think would save some hassle.
> 
> Sorry to be a pain, but I really would like some more time to catch up 
> and make some last changes. I haven't yet even looked at Johannes' 
> minimal filter flags implementation in the driver or Michael's fix.
> 
> Would you agree to let this wait until 2.6.25? You can hold me to that, 
> although Ulrich should also comment on if he thinks he'd be ready by then.

Fair enough, I'll remove the Z1211 driver during my next rebase.
-
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