netdev - Re: [PATCH 1/1] iwmc3200: add more SDIO device ids

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:	Mon, 24 Aug 2009 15:29:24 -0700
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	Tomas Winkler <tomasw@...il.com>
Cc:	davem@...emloft.net, netdev@...r.kernel.org,
	linux-wireless@...r.kernel.org, Greg KH <greg@...ah.com>
Subject: Re: [PATCH 1/1] iwmc3200: add more SDIO device ids

On Mon, Aug 24, 2009 at 3:20 PM, Tomas Winkler<tomasw@...il.com> wrote:
> On Tue, Aug 25, 2009 at 12:36 AM, Luis R. Rodriguez<mcgrof@...il.com> wrote:
>> On Mon, Aug 24, 2009 at 2:34 PM, Tomas Winkler<tomas.winkler@...el.com> wrote:
>>> add WiFi BGN SKU and WiMAX 2.4GHz SKU device ids
>>>
>>> Cc:inaky.perez-gonzalez@...el.com
>>> Cc:cindy.h.kao@...el.com
>>> Cc:yi.zhu@...el.com
>>> Signed-off-by: Tomas Winkler <tomas.winkler@...el.com>
>>
>> Since it seems we are preferring to not do this for PCI for cases
>> where the ID will only be used for 1 device perhaps its best to remove
>> all those ids and stuff them directly into the intel driver itself
>> that will use it.
>>
> I don't have strong opinion about it but this is the current habit
> IIRC there was a mail thread that explicitly asked to move SDIO IDs
> there,  of course I cannot locate it right now :(

Sure, understood, whoever maintains this should decide.

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