public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Bart Hartgers <bart.hartgers@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ondrej Zary <linux@rainbow-software.org>,
	ark3116_driver@auctionant.de
Subject: Re: New ark3116 driver - how to get included into kernel?
Date: Thu, 17 Sep 2009 23:15:29 -0700	[thread overview]
Message-ID: <20090918061529.GB7717@kroah.com> (raw)
In-Reply-To: <7eb6a4d80909170552na322914x23b65d60bb56e20d@mail.gmail.com>

On Thu, Sep 17, 2009 at 02:52:29PM +0200, Bart Hartgers wrote:
> (Sorry for sending an HTML-ized version of this mail before)
> 
> Hi All,
> 
> I managed to write an improved ark3116 driver after I figured out that
> it is just an 16450 UART with some USB glue logic.
> 
> The attached files can be compiled outside the kernel tree, and work
> for 2.6.31. However, I would like this driver to (eventually) end up
> in the kernel tree. In order to get there, who should I sent patches
> against what? I've contributed code to the kernel before, but not in
> the last 5 or so years, so I am a bit out of touch.

Take a look at the file, Documentation/SubmittingPatches, it should
describe what you need to do.

> Compared to the old ark3116 driver this one offers the following improvements:
>  - cts/rts handshake support
>  - break signalling
>  - line error detection

Why can't you just send patches adding support for these features to the
existing driver?  It shouldn't be that much different between the two
versions, right?

That's the preferred method, I'd like to not drop the existing one if at
all possible.

thanks,

greg k-h

  reply	other threads:[~2009-09-18  6:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7eb6a4d80909170549k7a19eb01s8975fe2c5f230cee@mail.gmail.com>
2009-09-17 12:52 ` New ark3116 driver - how to get included into kernel? Bart Hartgers
2009-09-18  6:15   ` Greg KH [this message]
2009-09-18 12:15     ` Bart Hartgers
2009-09-18 12:55       ` Oliver Neukum
2009-09-18 16:18       ` 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=20090918061529.GB7717@kroah.com \
    --to=greg@kroah.com \
    --cc=ark3116_driver@auctionant.de \
    --cc=bart.hartgers@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@rainbow-software.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