From: William Enck <wenck@wapu.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: [bk patches] 2.6.x net driver updates
Date: Thu, 7 Aug 2003 23:01:33 -0400 [thread overview]
Message-ID: <20030808030133.GA20401@chaos.byteworld.com> (raw)
In-Reply-To: <20030808020416.GA20116@chaos.byteworld.com>
On Thu, Aug 07, 2003 at 10:04:16PM -0400, William Enck wrote:
> The first set i was from -test2-bk7 and the second was from your patch.
> Your patch didn't cause the problem. I replied to your email because you
> had updates to orinoco_cs.c and I thought there was a chance your patch
> was supposed to fix it. I guess a reply was not the best thing to do,
> shall I start a new thread?
This looks like it is a totaly separate problem. I tested -mm5 and it
didn't work in there either. I'm going to start a new thread for this.
Will
--
William Enck
wenck@wapu.org
next prev parent reply other threads:[~2003-08-08 3:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 0:05 [bk patches] 2.6.x net driver updates Jeff Garzik
2003-08-08 1:36 ` William Enck
2003-08-08 1:41 ` Jeff Garzik
2003-08-08 2:04 ` William Enck
2003-08-08 3:01 ` William Enck [this message]
2003-09-11 19:54 Jeff Garzik
2003-09-20 19:27 Jeff Garzik
2003-09-26 1:02 Jeff Garzik
2003-09-27 5:20 ` Linus Torvalds
2003-09-27 11:55 [BK PATCHES] " Jeff Garzik
2003-09-28 14:45 [bk patches] " Jeff Garzik
2003-10-14 19:06 [BK PATCHES] " Jeff Garzik
2004-06-17 1:01 Jeff Garzik
2004-07-01 3:54 Jeff Garzik
2004-07-02 17:14 Jeff Garzik
2004-07-09 20:14 Jeff Garzik
2004-10-22 2:11 Jeff Garzik
2004-10-25 8:24 Jeff Garzik
2004-10-26 5:37 Jeff Garzik
2004-10-30 13:32 Jeff Garzik
2004-11-05 8:22 Jeff Garzik
2005-01-11 5:01 Jeff Garzik
2005-01-18 8:15 Jeff Garzik
2005-03-05 18:44 Jeff Garzik
2005-03-06 23:38 Jeff Garzik
2005-03-07 17:10 Jeff Garzik
2005-03-08 19:31 Jeff Garzik
2005-03-09 17:22 Jeff Garzik
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=20030808030133.GA20401@chaos.byteworld.com \
--to=wenck@wapu.org \
--cc=hch@infradead.org \
--cc=jgarzik@pobox.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 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.