kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: victorascroft@gmail.com (victorascroft at gmail.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Process for adding a new source(driver) to linux kernel tree
Date: Sat, 29 Aug 2015 16:14:45 +0530	[thread overview]
Message-ID: <20150829104445.GA965@Sanchayan-Arch> (raw)
In-Reply-To: <CAEwN+MDbDUoBsaEOOHeCbgK+dZqYthUwYO-KjanxDSno+s8fUQ@mail.gmail.com>

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

      parent reply	other threads:[~2015-08-29 10:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150829104445.GA965@Sanchayan-Arch \
    --to=victorascroft@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).