From: Greg KH <greg@kroah.com>
To: kernel1@jsl.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Keyspan USB/Serial Drivers for 2.4.20/2.4.21-pre4
Date: Thu, 20 Feb 2003 16:06:47 -0800 [thread overview]
Message-ID: <20030221000647.GA26468@kroah.com> (raw)
In-Reply-To: <200302202328.h1KNSaj26209@jsl.com>
On Thu, Feb 20, 2003 at 03:28:35PM -0800, System Administrator wrote:
> Hello List,
>
> I'm not sure why, but the current kernel source tree doesn't support some
> of the Keyspan USB/Serial adapter products (49WLC and MPR). There is code
> at: http://www.keyspan.com/support/linux/files/currentversion/rev2003jan31/
> but it only works with 2.4.18 or 2.4.19. Keyspan seems to think the code
> is current and they didn't want my patches. Here they are for posterity.
Any reason you didn't send this to the listed maintainer for these
drivers? :)
Thanks for doing this, but why did you modify the Config.in file so
much? That's not correct.
And does this patch work with the new devices?
thanks,
greg k-h
next prev parent reply other threads:[~2003-02-21 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 23:28 Keyspan USB/Serial Drivers for 2.4.20/2.4.21-pre4 System Administrator
2003-02-21 0:06 ` Greg KH [this message]
2003-02-21 17:28 ` [patch] " System Administrator
2003-02-28 21:14 ` 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=20030221000647.GA26468@kroah.com \
--to=greg@kroah.com \
--cc=kernel1@jsl.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