outreachy/moving a driver out of staging
mzoran at crowfest.net
Sun Mar 19 03:22:08 PDT 2017
On Sun, 2017-03-19 at 09:15 +0000, Russell King - ARM Linux wrote:
> 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:
> 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
> to the dmac_map_area() hack.
> So that one looks like it's resolved, so the TODO file is out of
> 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
I've actually been submitting changes to the TODO files as I've been
going. Just these days I'm not sure which tree things are being
applied to anymore.
So I'm assuming once all the TODO items are addressed, and everything
is checkpatch.pl clean it can be moved out of staging? I would assume
an existing subsystem would need to agree to accept it into their topic
More information about the linux-rpi-kernel