On Mon, Jul 23, 2007 at 01:03:47AM +0200, Tilman Schmidt wrote:
> Am 22.07.2007 21:30 schrieb Pete Zaitcev:
> > On Sun, 22 Jul 2007 16:44:24 +0200, Tilman Schmidt <[EMAIL PROTECTED]>
> > wrote:
> >
> >> Should I do something similar for drivers/isdn/{bas,usb}-gigaset.c?
> >> What exactly is the goal?
> >
> > In most cases of sweeping API changes in Linux kernel it's the respon-
> > sibility of whoever is doing the change to fix up the affected code.
>
> So I gather, although there doesn't seem to be universal consensus on that.
Well the goal is to never break the build. These prep patches end up
exposing a lot of real bugs in drivers where they are accessing this
field when they should not be doing so.
It will also make the eventual switch much easier to read and say "yes,
this is correct" if it doesn't have to do all of this other cleanup
along the way.
> > That said, we can help Alan and Co. if something gets overlooked.
>
> Yep. And as the Gigaset drivers are not located below drivers/usb they
> are in particular danger of being overlooked if it comes to sweeping
> changes of the USB infrastructure. That's why I asked.
Lots of drivers that use the USB interface are not under drivers/usb/
anymore, so don't worry, I am looking at all of them for these kinds of
changes :)
thanks,
greg k-h
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
