Adding Cc: staging maintainer and mailinglist. On Sep 26 Devin Heitmueller wrote: > On Sun, Sep 25, 2011 at 11:25 PM, Mauro Carvalho Chehab > <maurochehab@xxxxxxxxx> wrote: > >> Want to see more device support upstream? Optimize the process to > >> make it easy for the people who know the hardware and how to write the > >> drivers to get code upstream, and leave it to the "janitors" to work > >> out the codingstyle issues. > > > > The process you've just described exists already since Sept, 2008. > > It is called: > > /drivers/staging > > > > In summary, if you don't have a couple hours to make your driver to > > match Kernel Coding Style, just send it as is to /drivers/staging, c/c > > me and Greg KH, and that's it. > > PULL http://kernellabs.com/hg/~dheitmueller/v4l-dvb-80e/ > PULL http://kernellabs.com/hg/~dheitmueller/v4l-dvb-as102-2/ > > Have fun. > > The harder you make it to get code upstream, the more developers who > will just say "to hell with this". And *that* is why there are > thousands of lines of working drivers which various developers have in > out-of-tree drivers. Hi, perhaps a kind developer over at devel@driverdev could extract patches for staging out of the above mercurial repositories, and then folks can work on mainline inclusion. (Somebody who actually has such a device might be most motivated to do it.) No need to get angry that it hasn't happened yet. :-) It's just a matter of the right people joining the effort at the right time. Thanks Devin for the offer, -- Stefan Richter -=====-==-== =--= ==-== http://arcgraph.de/sr/ _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
