On Thu, Mar 29, 2007 at 07:22:36PM -0700, Greg KH wrote: > On Thu, Mar 29, 2007 at 02:31:12PM +0200, Oleg Verych wrote: > > usb-serial, ti_usb: fix usb configuration changing > > > > Remove bogus error messages, comments with script. > > Use new usb-configuration interface for usb-interface drivers. > > > > Cc: Linus Torvalds <[EMAIL PROTECTED]> > > Cc: Al Borchers <[EMAIL PROTECTED]> > > Signed-off-by: Oleg Verych <[EMAIL PROTECTED]> > > --- > > This tiny change uses new interface merged in 2.6.19 (yet author of > > it didn't find this driver to fix). > > > > Greg KH waits driver's author ack, while i already have it (in > > the linux-usb list): > > But we don't have it on this patch, which is what I require before I'm > going to be able to accept it, sorry.
I have device, i've done cosmetic changes Al requested, patch uses interface merged in 2.6.19 kernel. > I am waiting for Al to send this to me before I add it to my tree. As you might remember my first patch in December was with "orphan" note, mainly because of laking udev support in any distro, *two* static firmware blobs for different devices are in one driver (i.e plain memory waste), userspace firmware loader wasn't adopted (after more than three years in the kernel; younger driver didn't use it either). > And then, only after it gets some testing in the -mm releases, will I > send it on to Linus, as I have stated many times in the past. This patch have a *fix* for using feature, merged in 2.6.19. I don't think it's worth to wait another two month to get some progress in this direction. > So please, don't try to route around me just because you don't like the > proceedure we have in place here. So, if you are saying, that it's due to "procedure", why there are such obvious USB fixes after 2.6.21-rc5, hm? Also, why this change wasn't done in 2.6.19, i.e. `grep -i -r -e configuration drivers/usb/* | grep set` shows this driver and need of this crutch. Crutch, because, current usb configuration setting/changing are for usb-interface drivers only, as people explained me. Thus, i still think, there is a gap in usb-plugged device configuration chain, i.e current usb interface (not device) driver have no control over usb-configuration. > That's just rude. You are being informed. I've said many things to make it clear, that this change is useful, out of "procedure" since 2.6.19, needed by users, not so high in driver author's may-do list. Adding somebody else, who can judge (if time permits), is good to have a fair _dialog_ between us two (:. Thanks. ____ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
