From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Merging device drivers to LK tree
Date: Tue, 14 Mar 2017 05:45:30 +0800 [thread overview]
Message-ID: <20170313214530.GB5539@kroah.com> (raw)
In-Reply-To: <d8de5ffb-3f30-415e-e22d-789fbcf21c92@gmail.com>
On Mon, Mar 13, 2017 at 11:21:24PM +0300, alexhoppus wrote:
> Hello!
>
> I have several questions regarding how device drivers are merged into
> linux-kernel. First of all, I have found some document regarding
> submitting drivers to LK, but it looks like pretty out-dated,
> https://kernelnewbies.org/UpstreamMerge/SubmittingDrivers
> is this info still relevant? Or there is a new one?
Look in the kernel source tree at Documentation/SubmittingDrivers for
the latest version.
> Actually, I want to know more about the process. To start with this, I
> would like to ask an example question. Surfing through the kernel source
> I have found several ra-link usb wi-fi adapter drivers (rtl8188eu,
> rtl8192e, rtl8712 ...). Suppose one have datasheet that gives the
> possibility for writing a device driver for say rtlxxxxx based device.
> Can third-party person write & submit this driver to LK or this must be
> done explicitly by device vendor?
Anyone can submit a driver.
> What are the requirements from LK community side?
It has to match our coding style rules and pass our code review.
> Are there any license issues with this? (besides the author should
> publish code under GPL)
Nope, just has to be compatible with GPLv2.
Do you have a specific driver you wish to get merged that isn't already
in the tree?
thanks,
greg k-h
next prev parent reply other threads:[~2017-03-13 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 20:21 Merging device drivers to LK tree alexhoppus
2017-03-13 21:45 ` Greg KH [this message]
2017-03-14 19:54 ` alexhoppus
2017-03-14 20:37 ` valdis.kletnieks at vt.edu
2017-03-14 20:59 ` Bjørn Mork
2017-03-14 21:14 ` valdis.kletnieks at vt.edu
2017-03-14 23:46 ` 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=20170313214530.GB5539@kroah.com \
--to=greg@kroah.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).