From: David Gibson <hermes@gibson.dropbear.id.au>
To: Pavel Roskin <proski@gnu.org>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>,
jt@hpl.hp.com, Dan Williams <dcbw@redhat.com>
Subject: Re: [PATCH] Slowly update in-kernel orinoco drivers to upstream current CVS
Date: Thu, 15 Jul 2004 11:26:56 +1000 [thread overview]
Message-ID: <20040715012656.GD3697@zax> (raw)
In-Reply-To: <Pine.LNX.4.60.0407141605460.1799@marabou.research.att.com>
On Wed, Jul 14, 2004 at 04:15:59PM -0400, Pavel Roskin wrote:
> On Mon, 12 Jul 2004, Francois Romieu wrote:
>
> >A serie of patches is available for at:
> >http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.7-mm7
> >
> >It contains 12 patches and applies against 2.6.7-mm7. The patches are
> >commented. The comments are partly taken from the cvs log by Pavel Roskin.
>
> I hope the patches lead to the CVS version on the "for_linus" branch which
> has no compatibility code. I'm quite comfortable with the "for_linus" and
> "Standalone" branches.
>
> As for the HEAD branch, it has unfinished (skeleton only) prism_usb driver
> meant for Intersil Prism USB devices (such as DWL-122). It also has
> working orinoco_usb driver. Unfortunately, I don't feel good about that
> code. The way how this code is integrated with the common code is
> questionable. A lot of work would be needed to handle USB better.
> That's not something that could be done before the next release.
I concur.
> I'm very busy now and I don't have time to finish the little bits I
> planned for the 0.15 release. However, the CVS version on the "for_linus"
> branch is releasable and has no known regressions compared to any previous
> version. Feel free to apply the patches to the kernel now. I expect to
> have more time for free software in the end of August.
Good to hear.
> If David is OK, we could release the current code as version 0.15. I'm OK
> with it. I have to adapt my ambitions to my time constraints.
I'm reasonably comfortable with that. I now have a handful of things
to commit before 0.15 which I've picked up while doing the merge with
mainline, but it's just whitespace and other trivialities.
> I'll
> appreciate if my name is added to the MAINTAINERS file once the new driver
> is committed.
Absolutely. Haven't put that patch together yet, but it's coming :)
--
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-15 3:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 19:33 [PATCH] Slowly update in-kernel orinoco drivers to upstream current CVS Francois Romieu
2004-07-14 18:37 ` Jeff Garzik
2004-07-15 1:01 ` David Gibson
2004-07-17 11:45 ` Francois Romieu
2004-07-27 17:18 ` Jeff Garzik
2004-07-28 6:51 ` [0/15] orinoco merge preliminaries David Gibson
2004-07-28 6:53 ` [1/15] orinoco merge preliminaries - squash backwards compatibility David Gibson
2004-07-28 6:53 ` [2/15] orinoco merge preliminaries - rearrange code David Gibson
2004-07-28 6:54 ` [3/15] orinoco merge preliminaries - use netdev_priv() David Gibson
2004-07-28 6:54 ` [4/15] orinoco merge preliminaries - use ALIGN() David Gibson
2004-07-28 6:55 ` [5/15] orinoco merge preliminaries - use ARRAY_SIZE() David Gibson
2004-07-28 6:55 ` [6/15] orinoco merge preliminaries - spam stoppers David Gibson
2004-07-28 6:56 ` [7/15] orinoco merge preliminaries - comment/whitespace/spelling updates David Gibson
2004-07-28 6:57 ` [8/15] orinoco merge preliminaries - use BUG_ON() David Gibson
2004-07-28 6:58 ` [9/15] orinoco merge preliminaries - make things static David Gibson
2004-07-28 6:58 ` [10/15] orinoco merge preliminaries - miscelaneous David Gibson
2004-07-28 6:59 ` [11/15] orinoco merge preliminaries - use name/version macros David Gibson
2004-07-28 6:59 ` [12/15] orinoco merge preliminaries - remove unneeded #includes David Gibson
2004-07-28 7:00 ` [13/15] orinoco merge preliminaries - don't typedef structs David Gibson
2004-07-28 7:00 ` [14/15] orinoco merge preliminaries - more HW data David Gibson
2004-07-28 7:01 ` [15/15] orinoco merge preliminaries - update authorship information David Gibson
2004-07-28 16:55 ` Jeff Garzik
2004-07-28 17:36 ` [6/15] orinoco merge preliminaries - spam stoppers Matt Mackall
2004-07-28 22:50 ` [0/15] orinoco merge preliminaries Francois Romieu
2004-07-29 0:19 ` David Gibson
2004-07-29 23:19 ` Francois Romieu
2004-09-08 15:18 ` Dan Williams
2004-09-09 3:13 ` Jeff Garzik
2004-09-09 19:51 ` Francois Romieu
2004-07-14 20:15 ` [PATCH] Slowly update in-kernel orinoco drivers to upstream current CVS Pavel Roskin
2004-07-15 1:26 ` 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=20040715012656.GD3697@zax \
--to=hermes@gibson.dropbear.id.au \
--cc=dcbw@redhat.com \
--cc=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.org \
--cc=romieu@fr.zoreil.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