Hello Greg,
There's no TODO file because it would have been empty: There is nothing
to do, as far as I know.
I submitted this to staging because I failed to push the Xillybus driver
to non-staging back in 2013. In the end, the way in was through staging
+ a review that got it out a year later or so. So I expected the same story.
I'll submit a patch for this driver to char/xillybus/ soon.
Thanks,
Eli
On 13/12/20 16:41, Greg KH wrote:
Why add this driver to staging? All drivers in staging need a TODO file
that lists what is needed to be done to it in order to get it out of
staging. Why not just submit it to the "real" part of the kernel?
thanks,
greg k-h
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
