From: Stephen Evanchik <evanchsa@clarkson.edu>
To: David Gibson <hermes@gibson.dropbear.id.au>,
Adam Kropelin <akropel1@rochester.rr.com>
Cc: linux-kernel@vger.kernel.org,
orinoco-users@lists.sourceforge.net, dhinds@sonic.net
Subject: Re: [Orinoco-users] [PATCH] orinoco_plx-0.13b backport to kernel 2.2
Date: Sun, 5 Jan 2003 19:25:45 -0500 [thread overview]
Message-ID: <200301051925.45507.evanchsa@clarkson.edu> (raw)
In-Reply-To: <20030106000929.GC18808@zax.zax>
David,
On Sunday 05 January 2003 19:09, David Gibson wrote:
| Eck... be aware that the "testing" version, although labelled 0.13b
| may not be the final 0.13b version.
More than likely it won't (your call though), I was using the "testing"
version when I discovered the problems as per my last email to you. I'll
have some more details sometime today or tomorrow.
Stephen Evanchik
next prev parent reply other threads:[~2003-01-06 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 23:19 [PATCH] orinoco_plx-0.13b backport to kernel 2.2 Adam Kropelin
2003-01-06 0:09 ` [Orinoco-users] " David Gibson
2003-01-06 0:25 ` Stephen Evanchik [this message]
2003-01-06 0:48 ` Adam Kropelin
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=200301051925.45507.evanchsa@clarkson.edu \
--to=evanchsa@clarkson.edu \
--cc=akropel1@rochester.rr.com \
--cc=dhinds@sonic.net \
--cc=hermes@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=orinoco-users@lists.sourceforge.net \
/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