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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1ba2fa240908241520q5be2060co145ec0745954dcf0@mail.gmail.com>
Date:	Tue, 25 Aug 2009 01:20:14 +0300
From:	Tomas Winkler <tomasw@...il.com>
To:	"Luis R. Rodriguez" <mcgrof@...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 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 :(

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