From: Greg KH <gregkh@linuxfoundation.org>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Mark Hounschell <markh@compro.net>,
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 09:03:48 -0700 [thread overview]
Message-ID: <20130426160348.GA28863@kroah.com> (raw)
In-Reply-To: <1366990765.3452.50.camel@thor.lan>
On Fri, Apr 26, 2013 at 11:39:25AM -0400, Peter Hurley wrote:
> On Fri, 2013-04-26 at 08:19 -0700, Greg KH wrote:
> > On Fri, Apr 26, 2013 at 11:10:14AM -0400, Mark Hounschell wrote:
> > > >Also, any reason why these drivers aren't in the main kernel tree? If
> > > >they were, all of this work would have been done for you :)
> > > >
> > >
> > > Yes, I wish they were in the kernel. I've had to maintain them since
> > > the 2.6 days because Digi just won't do it and their cards do what
> > > we need quite well and are still current products. Ya, you can buy a
> > > brand new one but the latest kernel supported is 2.6. I think Digi
> > > at one point long ago may have tried the "in kernel" route but you
> > > probably know more about that than I do.
> > >
> > > Since 2.6, the maintenance on these hasn't been to bad, until udev
> > > came along. But I guess after 3.4 the tty layer is going through
> > > quite some changes that I have yet to understand.
> >
> > And there will be lots more changes happening to it in the future. Why
> > not submit the drivers now (after you get them working)?
>
> Probably not Mark's (or Compro's) code to submit.
If it's a GPL driver, anyone can submit it.
However, if the original copyright owner doesn't want it to be
submitted, we will be glad to take that under consideration.
Mark, what's the reason this has never been submitted?
thanks,
greg k-h
next prev parent reply other threads:[~2013-04-26 16:03 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 [this message]
2013-04-26 17:58 ` Mark Hounschell
2013-04-26 23:21 ` Greg KH
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=20130426160348.GA28863@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).