Re: RFC/patch 5/6: usb: split usb_new_device for clarity and refactoring
David Brownell <[email protected]>
| Newsgroups | gmane.linux.usb.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tuesday 24 April 2007, Inaky Perez-Gonzalez wrote: > This patch takes hub.c:usb_new_device() and splits it in three parts: > > ... > > When a device is authorized connection, we need to run through the > hoops we didn't run when it was connected but not authorized, which is > basically parsing the configurations and probing > them. __usb_configure_device() will do that for us. Yeah, this part sounds unavoidable. But the "__usb_*()" names are not needed when the functions aren't going to be exported out of that one file. And as I noted earlier, I think we already have a way to represent devices in this "not yet authenticated" state (you do seem consistent about misusing the term "authorized"!), so a new usbcore flag isn't needed. - Dave ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel