> > Feel like providing a patch?
>
> Well, I've never "patched" before ... is there some docs on the process?
Start with: /usr/src/linux/Documentation/SubmittingPatches ...
For a single file,
diff -u old.c new.c > my.patch
and you can test it on a new kernel by
patch -p0 < my.patch
or revert it by
patch -p0 -R < my.patch
It's also good practice to review patches to make sure you're only
changing what you intended to change. When you find there's some
extra change, it's often easy to edit the patch file to delete that chunk
of the diff ... but "patch -p0 --dry-run < my.patch" to be sure you didn't
corrupt the patchfile.
- Dave
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
