Greg, On 20 October 2017 at 20:31, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Fri, Oct 20, 2017 at 08:15:23PM +0530, PrasannaKumar Muralidharan wrote: >> Hi Greg, >> >> On 20 October 2017 at 12:40, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: >> > On Fri, Oct 20, 2017 at 12:15:56PM +0530, PrasannaKumar Muralidharan wrote: >> >> Hi Christian, >> >> >> >> It has been a couple of years since most was added to the staging >> >> tree. Except for review the TODO list does not mention things that are >> >> required to destage it. Wondering why most is still in staging tree. >> > >> > Did you see the big set of patches that were just posted to the list a >> > few days ago for this subsystem? >> > >> > Look at them for an example of what still needs to be done :) >> >> Looking at the patches triggered me look into the TODO file which did >> not mention any thing to do other than review. >> >> > Any specific reason why you are asking this? Do you use these drivers? >> >> I do not use this driver. I am interested in automotive stuff. >> >> I always thought that the driver is ready to be destaged. Recent patch >> set proves me wrong. Once it gets merged I am wondering what would be >> left to do. > > Review the code then and see if you find any problems that would keep it > from being moved to the main part of the kernel tree? Look at the > user/kernel api, the interaction with the driver model, and other > obvious things (sparse and checkpatch.pl clean.) That's all that is > needed. I do not have info on what qualities are required for a driver to go out of staging. I can give a hand in code review. > If you feel it is all good to go, letting everyone know is also > important. Sure I will do so. > thanks, > > greg k-h Thanks, PrasannaKumar _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
