All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: WCH Tech Group <tech@winchiphead.com>
Cc: johan@kernel.org, konstantin.shkolnyy@gmail.com,
	pberger@brimson.com, david.ward@ll.mit.edu, m.othacehe@gmail.com,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: 转发: [PATCH] usb: serial: update CH34x driver in drivers/usb/serial
Date: Fri, 24 Jun 2016 08:09:51 -0700	[thread overview]
Message-ID: <20160624150951.GA5719@kroah.com> (raw)
In-Reply-To: <002401d1cddb$2f70ab60$8e520220$@com>

On Fri, Jun 24, 2016 at 01:42:24PM +0800, WCH Tech Group wrote:
> 	There are several reasons why we decided to revoke the old one after
> communicating with the author of 
> ch341.c (Frank A Kingswood <frank@kingswood-consulting.co.uk>), first of all
> we want the driver to support both ch341 and
> ch340 chips, so we changed the driver name from "ch341.c" to "ch34x.c",

No need to rename the driver to support multiple chips.  Keep it the
same name, and just add the new device support.  That's how we do it for
lots and lots of Linux drivers, the name doesn't really matter that
much (look at the option.c driver for one such example.)

> secondly the new driver and old one are coded
> by different authors, in fact there's no connection between them.

Ok, but the functionality is the same, so please just fix up the
existing driver to add support for the new device, and fix any existing
bugs.

In Linux you don't get to just delete a working driver, you have to
evolve code over time, sending patches that do one logical thing at a
time so that people can properly review them.  Your patch is not how
this is supposed to happen at all.

So please just break up your changes into small logical ones, and send a
series of patches adding the new device support and fix up any known
bugs.

After that is all done, if you _really_ want to rename the driver, then
we can discuss that, but first do the work to evolve the driver, as that
is much more difficult.

thanks,

greg k-h

       reply	other threads:[~2016-06-24 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <002401d1cddb$2f70ab60$8e520220$@com>
2016-06-24 15:09 ` Greg KH [this message]
     [not found]   ` <CAB=c7Tr8FhXNJyMgviLbmNcWQKNWhum_16zRnym0tyP_f9v94w@mail.gmail.com>
2016-09-15  5:56     ` 转发: [PATCH] usb: serial: update CH34x driver in drivers/usb/serial Greg KH
2016-09-15 10:19       ` Aidan Thornton
2016-09-15 11:00         ` Johan Hovold
2016-09-20 19:38     ` Grigori Goronzy

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=20160624150951.GA5719@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=david.ward@ll.mit.edu \
    --cc=johan@kernel.org \
    --cc=konstantin.shkolnyy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.othacehe@gmail.com \
    --cc=pberger@brimson.com \
    --cc=tech@winchiphead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.