linux-kernel - Re: New ark3116 driver - how to get included into kernel?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 Sep 2009 23:15:29 -0700
From:	Greg KH <greg@...ah.com>
To:	Bart Hartgers <bart.hartgers@...il.com>
Cc:	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	Ondrej Zary <linux@...nbow-software.org>,
	ark3116_driver@...tionant.de
Subject: Re: New ark3116 driver - how to get included into kernel?

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/