public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan Rose <stephan@eciinternational.de>
To: Greg KH <greg@kroah.com>
Cc: David Newall <davidn@davidnewall.com>,
	Jiri Slaby <jirislaby@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: PL2303 Driver missing support for USB to Serial Cable
Date: Wed, 20 Feb 2008 09:46:03 -0500	[thread overview]
Message-ID: <1203518763.7002.0.camel@software> (raw)
In-Reply-To: <20080218050603.GB15141@kroah.com>


On Sun, 2008-02-17 at 21:06 -0800, Greg KH wrote:
> On Sat, Feb 16, 2008 at 11:35:16PM +1030, David Newall wrote:
> > Stephan,
> > 
> > Jiri Slaby wrote:
> > > On 02/14/2008 03:57 PM, Stephan Rose wrote:
> > >> I recently purchased a USB->Com Port serial cable from Radio Shack
> > >> (Model number 26-183) which did no seem to want to work. After looking
> > >> into it I discovered that it is based on the Prolific chipset using the
> > >> PL2303 driver.
> > >
> > > Well, would you mind creating, testing and posting a patch?
> > 
> > 
> > You needn't bother.  As far as I'm concerned, what you sent is
> > sufficient and, as I am currently working on the pl2303 driver, you can
> > rest assured that it will be included in the patch that I send.
> 
> That might be pretty tough to do, as it's already in the 2.6.25-rc2
> release :)
> 
> And please, patches need to be one-thing-per-patch.  Don't try to mix
> cleanups, bug fixes, and also new devices ids all in one patch.
> 
> Stephan, thanks for the report, but someone beat you to it by a few
> weeks already, the driver is updated.

No problem, glad it's already in! :)

Thanks,

Stephan


      reply	other threads:[~2008-02-20 14:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 14:57 PL2303 Driver missing support for USB to Serial Cable Stephan Rose
2008-02-16 12:52 ` Jiri Slaby
2008-02-16 13:05   ` David Newall
2008-02-18  5:06     ` Greg KH
2008-02-20 14:46       ` Stephan Rose [this message]

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=1203518763.7002.0.camel@software \
    --to=stephan@eciinternational.de \
    --cc=davidn@davidnewall.com \
    --cc=greg@kroah.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.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