kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
* Process for adding a new source(driver) to linux kernel tree
@ 2015-08-28 10:58 Raul Piper
  2015-08-29  6:37 ` Raul Piper
  2015-08-29 10:44 ` victorascroft at gmail.com
  0 siblings, 2 replies; 3+ messages in thread
From: Raul Piper @ 2015-08-28 10:58 UTC (permalink / raw)
  To: kernelnewbies

HI,
I wanted to know what is the process for adding a new source(say driver) to
the kernel tree.I am not asking for how to add a driver ( like modifying
make file, Kconfig, adding driver to staging or my_driver folder) but the
process for adding it to the source tree Like :
- which branch to add
-Any format of the files or directory
- whom to mail(maintainer,developer,tester,etc)
- Do I have to upload any test results
- Do I have to build it for any minimum number of platforms
- Do I need to send mail to the maintainer of that subsystem or fraemwork?
- Any tool to run the coding conventions checks,bugs checks,Memory leak
checks,etc
Kindly let me know.
Thanks and Rgds,
Rp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150828/4889b02a/attachment.html 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Process for adding a new source(driver) to linux kernel tree
  2015-08-28 10:58 Process for adding a new source(driver) to linux kernel tree Raul Piper
@ 2015-08-29  6:37 ` Raul Piper
  2015-08-29 10:44 ` victorascroft at gmail.com
  1 sibling, 0 replies; 3+ messages in thread
From: Raul Piper @ 2015-08-29  6:37 UTC (permalink / raw)
  To: kernelnewbies

any comments !!

On Fri, Aug 28, 2015 at 4:28 PM, Raul Piper <raulpblooper@gmail.com> wrote:

> HI,
> I wanted to know what is the process for adding a new source(say driver)
> to the kernel tree.I am not asking for how to add a driver ( like modifying
> make file, Kconfig, adding driver to staging or my_driver folder) but the
> process for adding it to the source tree Like :
> - which branch to add
> -Any format of the files or directory
> - whom to mail(maintainer,developer,tester,etc)
> - Do I have to upload any test results
> - Do I have to build it for any minimum number of platforms
> - Do I need to send mail to the maintainer of that subsystem or fraemwork?
> - Any tool to run the coding conventions checks,bugs checks,Memory leak
> checks,etc
> Kindly let me know.
> Thanks and Rgds,
> Rp
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150829/681d68f6/attachment.html 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Process for adding a new source(driver) to linux kernel tree
  2015-08-28 10:58 Process for adding a new source(driver) to linux kernel tree Raul Piper
  2015-08-29  6:37 ` Raul Piper
@ 2015-08-29 10:44 ` victorascroft at gmail.com
  1 sibling, 0 replies; 3+ messages in thread
From: victorascroft at gmail.com @ 2015-08-29 10:44 UTC (permalink / raw)
  To: kernelnewbies

On 15-08-28 16:28:36, Raul Piper wrote:
> HI,
> I wanted to know what is the process for adding a new source(say driver) to
> the kernel tree.I am not asking for how to add a driver ( like modifying
> make file, Kconfig, adding driver to staging or my_driver folder) but the
> process for adding it to the source tree Like :
> - which branch to add

This depends on the subsystem the driver will use. For eg. IIO or USB. Accordingly
it the patches should be generated on top of the said subsystem maintainer's branch.
So for USB it will be greg's usb git branch.

> -Any format of the files or directory

What do you mean here?

> - whom to mail(maintainer,developer,tester,etc)
> - Do I have to upload any test results

This depends. If you were to be writing a NAND driver, you would have to provide
mtdtests results.

> - Do I have to build it for any minimum number of platforms

Some predefined configs should be build checked.

> - Do I need to send mail to the maintainer of that subsystem or fraemwork?

Of course!!!! How else will you submit your work? Run getmaintainers.pl on
your patchset.

> - Any tool to run the coding conventions checks,bugs checks,Memory leak
> checks,etc

Coding conventions can be checked with checkpatch.pl. The rest is suppose
to be non existent in the driver you write!!!!

http://lxr.free-electrons.com/source/Documentation/development-process/
http://lxr.free-electrons.com/source/Documentation/CodingStyle
http://lxr.free-electrons.com/source/Documentation/SubmittingDrivers
http://lxr.free-electrons.com/source/Documentation/SubmittingPatches

> Kindly let me know.
> Thanks and Rgds,
> Rp

> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-08-29 10:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-08-28 10:58 Process for adding a new source(driver) to linux kernel tree Raul Piper
2015-08-29  6:37 ` Raul Piper
2015-08-29 10:44 ` victorascroft at gmail.com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).