From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Hounschell <markh@compro.net>
Cc: Peter Hurley <peter@hurleysoftware.com>,
linux-serial@vger.kernel.org, Mark Hounschell <dmarkh@cfl.rr.com>
Subject: Re: Out of tree GPL serial tty driver help?
Date: Fri, 26 Apr 2013 16:21:52 -0700 [thread overview]
Message-ID: <20130426232152.GA10407@kroah.com> (raw)
In-Reply-To: <517AC036.7000009@compro.net>
On Fri, Apr 26, 2013 at 01:58:14PM -0400, Mark Hounschell wrote:
> As for the Digi card driver/drivers, I can't say why not. There is a
> remnant of the actual one this thread is pertaining to in
> ./Documentation/serial/digiepca.txt. I've never submitted it or any
> of their others I have to maintain because I didn't know I could nor
> would know how to start. I thought that Digi would have had to do
> it.
>
> As far as Compro's drivers go, I think we have just been a little
> wary/unknowing of what it would take and what the results of the
> effort would actually be. Would they still do what _we_ needed them
> to do? Are we kernel savvy enough to get them to a state you would
> accept? etc... We do understand that if they were in the kernel that
> the best qualified people would be the ones that "kept them current"
> with the latest kernel changes. It's certainly something that no one
> here would object to doing. Are you the man to talk to? What is the
> actual process?
Yes, I'm the person to talk to about doing this, we can take it off-list
if you want.
But, for some reading material about the process, take a look at
Documentation/SubmittingDrivers and Documentation/SubmittingPatches in
the kernel source tree.
Also, if you don't want to do the work, I, and a bunch of others, will
be glad to do it for you, for free, see the site linuxdriverproject.org
for some details about that.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2013-04-26 23:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 17:44 Out of tree GPL serial tty driver help? Mark Hounschell
2013-04-25 21:41 ` Peter Hurley
2013-04-26 12:58 ` Mark Hounschell
2013-04-26 13:45 ` Peter Hurley
2013-04-26 14:28 ` Mark Hounschell
2013-04-26 14:35 ` Greg KH
2013-04-26 15:10 ` Mark Hounschell
2013-04-26 15:19 ` Greg KH
2013-04-26 15:39 ` Peter Hurley
2013-04-26 16:03 ` Greg KH
2013-04-26 17:58 ` Mark Hounschell
2013-04-26 23:21 ` Greg KH [this message]
2013-04-26 16:37 ` Peter Hurley
2013-04-26 18:17 ` Mark Hounschell
2013-04-26 19:51 ` Peter Hurley
2013-04-26 20:26 ` Mark Hounschell
2013-04-26 21:49 ` Peter Hurley
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=20130426232152.GA10407@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dmarkh@cfl.rr.com \
--cc=linux-serial@vger.kernel.org \
--cc=markh@compro.net \
--cc=peter@hurleysoftware.com \
/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).