On Sun, Mar 19, 2017 at 12:37:47AM -0700, Michael Zoran wrote: > I just noticed this e-mail. What exactly is the requirement to get a > driver or subsystem out of staging? This is why each driver in staging is supposed to have a TODO file listing each point that needs to be addressed, and when each point is addressed, the TODO file should be updated. The TODO file tells people what the remaining faults are with the driver. I see that there's a todo file here: drivers/staging/vc04_services/interface/vchi/TODO and the very first thing I looked at was: - Figure out an alternative to the dmac_map_area() hack. $ grep -r dmac_map_area drivers/staging/vc04_services/interface/vchi drivers/staging/vc04_services/interface/vchi/TODO: - Figure out an alternative to the dmac_map_area() hack. So that one looks like it's resolved, so the TODO file is out of date. The first step, therefore, is to get the TODO files updated with the work that has been done, so it's possible to know what work remains. I notice also that drivers/staging/vc04_services/interface/vchiq_arm does not have a TODO file, so that needs reviewing and a TODO file generated. -- RMK's Patch system: http://www.armlinux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
