Am Freitag 29 Mai 2009 13:05:16 schrieb Jonathan Michalon: > Jonathan Michalon a écrit : > > GWater a écrit : > >> 2. I don't know LKML procedure. > > > > Neither do I but it's time to learn. I'll read some doc about that > > tomorrow. > > I've a little investigated. This is what I've noticed. > > http://www.kernel.org/doc/Documentation/SubmittingDrivers > is a good basis, I don't know in which state is your source code, but it > seems to have to be checked against these requirements. > > The MAINTAINERS file in the kernel tree: > 2. Try to release a few ALPHA test versions to the net. Announce > them onto the kernel channel and await results. This is especially > important for device drivers, because often that's the only way > you will find things like the fact version 3 firmware needs > a magic fix you didn't know about, or some clown changed the > chips on a board and not its name. (Don't laugh! Look at the > SMC etherpower for that.) > > I think we should make a tarball ready-to-test, no? > Next, there is no maintainer for the whole media/video stuff but a mailing > list: [email protected] > This list may IMHO be used to announce the ALPHA presented before. > After mailing to the list, we may be driven by people knowing exactly what > to do in the specific case of this driver. > > Does all this seem reasonable to you? > What pending patches / ideas is there? If SXGA is not ready, I think this > doesn't matter since it may be part of a latter update so there is not too > much to release in one block. > > Johndescs > > P.S. If you think I'm too quick and going in a hurry, let me know... I just > hope to help this being available for the whole community. > > > --~--~---------~--~----~------------~-------~--~----~ > Lets make microdia webcams plug'n play, (currently plug'n pray) > To post to this group, send email to [email protected] > Visit us online https://groups.google.com/group/microdia > -~----------~----~----~----~------~----~------~--~---
I think most we comply with most of the things mentioned: - Copyright and License integrity were insured from the beginning. - coding style has been fixed - struct usb_sn9c20x mirrors the hardware(clarity) - we have suspend/resume - V4L2 support - at least x86 and x86_64 have been tested Do we want a MAINTAINER flag for our driver? Looking back on recent activity I don't think so. Short: I agree. What tarball do you want to submit - our master or our prepare-for-kernel branch? What happened to the famous git-pull requests? GWater
signature.asc
Description: This is a digitally signed message part.
