From: Greg KH <greg@kroah.com>
To: kernel1@jsl.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Re: Keyspan USB/Serial Drivers for 2.4.20/2.4.21-pre4
Date: Fri, 28 Feb 2003 13:14:41 -0800 [thread overview]
Message-ID: <20030228211441.GC29266@kroah.com> (raw)
In-Reply-To: <200302211728.h1LHSS720755@jsl.com>
On Fri, Feb 21, 2003 at 09:28:28AM -0800, System Administrator wrote:
>
> Please excuse my mistakes. That was my very first post to the list even
> though I've been reading it for many years. I wasn't entirely sure how to
> get this out there. I'm glad you noticed it Greg :)
>
> You're right. the Config.in file didn't need all those changes. I mistakedly
> diffed against the wrong file.
>
> The 49WLC device works fine with this patch. I have not tested the MPR but
> it should work too.
>
> Below is a better patch.
Thanks, I've applied this patch (and the firmware files) to my 2.4 and
2.5 trees, and will be sending them onward soon.
greg k-h
prev parent reply other threads:[~2003-02-28 21:13 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
2003-02-21 17:28 ` [patch] " System Administrator
2003-02-28 21:14 ` Greg KH [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=20030228211441.GC29266@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