public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Dan Williams <dcbw@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH] Update in-kernel orinoco drivers to upstream current CVS
Date: Fri, 02 Jul 2004 15:25:33 -0400	[thread overview]
Message-ID: <40E5B6AD.6060904@pobox.com> (raw)
In-Reply-To: <1088795498.18039.25.camel@dcbw.boston.redhat.com>

Dan Williams wrote:
> Hi,
> 
> This patch is simply the fixed-up diff between the kernel's current
> 0.13e version and the upstream 0.15rc1+ version from savannah CVS.
> 0.15rc1 has been out for a couple months now and seems stable.
> 
> The major benefits that this newer version brings are, of course, many
> bugfixes, but best of all wireless scanning support for the Orinoco line
> of cards.
> 
> http://people.redhat.com/dcbw/linux-2.6.7-orinoco.patch.bz2
> 
> Dan Williams
> Red Hat, Inc.


I'm desperately hoping that someone will split this up into multiple 
patches...

	Jeff



  reply	other threads:[~2004-07-02 19:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02 19:11 [PATCH] Update in-kernel orinoco drivers to upstream current CVS Dan Williams
2004-07-02 19:25 ` Jeff Garzik [this message]
2004-07-04  2:01   ` David Gibson
  -- strict thread matches above, loose matches on Subject: below --
2004-07-02 22:26 Jean Tourrilhes
2004-07-02 23:07 ` Francois Romieu
2004-07-03 20:15   ` Francois Romieu
2004-07-03 23:11   ` Francois Romieu
2004-07-04  2:13   ` David Gibson
2004-07-04 17:17     ` Francois Romieu
2004-07-05 23:14       ` Francois Romieu
2004-07-05 23:39         ` Jeff Garzik
2004-07-06 22:54           ` Francois Romieu
2004-07-07  1:25             ` Michael Clark
2004-07-07 18:50               ` Pavel Roskin
2004-07-08 22:04                 ` Jeff Garzik
2004-07-08 23:17             ` Francois Romieu
2004-07-08 23:30               ` Jeff Garzik
2004-07-03  6:08 ` 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=40E5B6AD.6060904@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=dcbw@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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