linux-kernel - Re: [stable] Wanted: Allow adding new device IDs during the -stable cycle

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: <4655F932.20006@garzik.org>
Date:	Thu, 24 May 2007 16:44:34 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	David Hollis <dhollis@...ehollis.com>
CC:	Greg KH <greg@...ah.com>, Dave Jones <davej@...hat.com>,
	Chuck Ebbert <cebbert@...hat.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: [stable] Wanted: Allow adding new device IDs during the	-stable
 cycle

David Hollis wrote:
> With the asix.c driver, you can't just add the USB IDs and have it work.
> Each ID also needs to be told which driver structure to use, since the
> driver itself supports three similar, but distinct chips.  Adding the
> IDs to the driver itself is naturally trivial, but adding via sysfs or
> the like doesn't work.  I would imagine that there are other drivers
> that operate quite similarly.

As is evident from the patches that do upstream (a requirement for 
-stable), it depends on the driver.  Some drivers work just fine with a 
simple ID addition.

Review the thread, we are just talking about the patches where adding an 
ID is the only work necessary.

	Jeff


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/