All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jacko Dirks <jdirks.linuxdev@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Location of files for a new driver
Date: Tue, 5 May 2020 16:20:32 +0200	[thread overview]
Message-ID: <20200505142032.GA793696@kroah.com> (raw)
In-Reply-To: <20200505135828.GA466217@vasteMachine>

On Tue, May 05, 2020 at 03:58:28PM +0200, Jacko Dirks wrote:
> Hello,
> 
> I am starting to work on a new driver. I think the actual driver
> (c file) needs to be placed in drivers/staging/subdir (am I 
> correct?).

drivers/staging/ is only for code that needs lots and lots of work to
get into the "real" part of the kernel.  It also requires a TODO file
that lists what is left to do to get it out of that location.

If you can write that TODO list, it's almost always easier to just do
that work yourself and then get the code merged into the real part of
the kernel than to put it into drivers/staging/

> But I also need to edit existing dts and dtsi files and I
> also need to introduce a new overlay. Where do I place those changes and
> new files? 

It all depends on what you are writing.  What exactly does this code do?
That will determine where it goes in the kernel tree.

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2020-05-05 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 13:58 Location of files for a new driver Jacko Dirks
2020-05-05 14:20 ` Greg KH [this message]
2020-05-05 14:38   ` Jacko Dirks
2020-05-05 18:05     ` Greg KH

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=20200505142032.GA793696@kroah.com \
    --to=greg@kroah.com \
    --cc=jdirks.linuxdev@gmail.com \
    --cc=kernelnewbies@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.