On Thu, Jan 13, 2022 at 07:54:19PM +0100, Philipp Hortmann wrote: > On 1/13/22 4:33 PM, Greg KH wrote: > > On Thu, Jan 13, 2022 at 07:39:38AM +0100, Philipp Hortmann wrote: > > > On 1/12/22 10:54 AM, Greg KH wrote: > > > > That driver tried to be an example for an unknown device, doing multiple > > > > different things that no single driver/device would probably ever need. > > > > Also it can almost always just be replaced with a simple userspace > > > > program using libusb, as I bet your driver could be replaced with as > > > > well, right? > > > Yes it can be replaced by a userspace program but even this is not required. > > It is an issue if you are trying to write a new driver. We do not take > > new drivers into the kernel tree if they can be in the kernel instead. > > > > Sorry I did not clearly express what I plan to do. I plan to do maintenance > and bug fixes on the kernel. That's wonderful, try starting out in drivers/staging/*/TODO for lots of things that need work. Messing around with old USB drivers that "just work" and you don't have the hardware for, might be a tough thing to work on as a beginning task. No need to touch things that no one is complaining about if you can help it :) thanks, greg k-h _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
