netdev - RE: [RFC] iwmc3200top: remove driver for unavailable hardware

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] [day] [month] [year] [list]

Message-ID: <3A78FAA0EC814D4B8ECC99B3AB32B3320812EBC9@fmsmsx110.amr.corp.intel.com>
Date:	Tue, 26 Jun 2012 21:21:34 +0000
From:	"Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@...el.com>
To:	"John W. Linville" <linville@...driver.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:	"Ortiz, Samuel" <samuel.ortiz@...el.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>
Subject: RE: [RFC] iwmc3200top: remove driver for unavailable hardware

Hi  John

> From: John W. Linville [mailto:linville@...driver.com]
> Subject: [RFC] iwmc3200top: remove driver for unavailable hardware
> 
> From: "John W. Linville" <linville@...driver.com>
> 
> This hardware never became available to normal humans.  Leaving this
> driver imposes unwelcome maintenance costs for no clear benefit.
> 
> Signed-off-by: John W. Linville <linville@...driver.com>
> ---
> Can't remove this just yet, as it is selected by the i2400m wimax
> driver.  The 3200 bits of that driver seem a bit intertwined with the
> rest of the driver.
> 
> Are there any other SDIO parts for i2400m?  Does anyone have any other
> guidance on how I can safely make i2400m be independent of iwmc3200
> support?

It should be pretty straight forward: remove the dependency. In fact, you
are very right--all the sdio code should be removed, as there are no SDIO
parts in the market, to the best of my knowledge.

Yank anything hitting a grep on sdio in i2400m/ (*sdio*) and the Makefile
entries, as well as the Kconfig. That should take care of it.

--
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