> How did you generate this one? The white-space issue is gone, but now > it's a "p0" patch again (without the root directory in the paths) so > checkpatch complains and it does not apply using git am (with the normal > settings anyway). > > Again, I can fix this up unless you prefer to respin. We have until the > end of the merge window to get it right. :)
Hi, Sorry about that. This time I took the time to do a proper linux git-clone and generated the patch with git instead of manually tweaking the diff output. Unfortunately I have a diff.noprefix setting for my daily workflow and I forgot about this point ... Please fix the patch, I guess it's just a matter of adding a/ b/ in front of the paths. Initially I just submitted a raw diff to convince you about the issue and better highlight it. Since it was basically a one-liner, I was not intending to go into the full fledged process of patch submission. Now this is getting a bit out of control and generates more noise than necessary :) My apologies. Keep me informed if/when it goes into the kernel, most important is to get this eventually fixed :) [actually most important for me would be to be able to programmatically get the actual latency setting as an integer - as in libftdi -, but I see no easy way to add this, without an extra specific ioctl(2)] -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
