On Wednesday 27 March 2002 19:46, Greg KH wrote:
> On Wed, Mar 27, 2002 at 03:33:20PM +0100, Nemosoft Unv. wrote:
> > Then why does nobody do it? It's all I'm asking....
>
> It's a pain in the butt at times, and much faster to fix something that
> you just broke, by patching everyplace in the kernel you broke.
>
> Look, someone changed the v4l core code.  This broke your driver (and a
> lot of other drivers.)  So they then went and fixed them all up.  This
> is usually one of the requirements for someone changing a kernel api.

*sigh* I think we're cross-talking here. I don't mind people fixing up my 
driver because they changes something 10 include files away. Fine. But 
*tell* me. For the very simple reason I usually jump a few kernel versions 
and, as in the case of 2.5, several different subsystems are changed, the 
changes can become somewhat overwhelming (which I had to patch in by hand 
:-( ). And just when I though I had caught up, well... :-/

> Might I suggest a good work environment that allows you to merge kernel
> updates easily and allow you to see when changes happen to your code?

But of course. What did you have in mind?

- Nemosoft

_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to