From: David Gibson <david@gibson.dropbear.id.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Dan Williams <dcbw@redhat.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [PATCH] Update in-kernel orinoco drivers to upstream current CVS
Date: Sun, 4 Jul 2004 12:01:06 +1000 [thread overview]
Message-ID: <20040704020106.GB25992@zax> (raw)
In-Reply-To: <40E5B6AD.6060904@pobox.com>
On Fri, Jul 02, 2004 at 03:25:33PM -0400, Jeff Garzik wrote:
> 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...
Urg, yes. I've dropped the ball badly on this. I've done very, very
little work on the driver for well over a year now and the changes
have built up to a megapatch. I really does need to be broken up, but
the chances of me finding the time and motivation to do so are not
looking good.
--
David Gibson | For every complex problem there is a
david AT gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
prev parent reply other threads:[~2004-07-04 2:01 UTC|newest]
Thread overview: 3+ 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
2004-07-04 2:01 ` David Gibson [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=20040704020106.GB25992@zax \
--to=david@gibson.dropbear.id.au \
--cc=dcbw@redhat.com \
--cc=jgarzik@pobox.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;
as well as URLs for NNTP newsgroup(s).