From: David Gibson <hermes@gibson.dropbear.id.au>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: jt@hpl.hp.com, Jeff Garzik <jgarzik@pobox.com>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Dan Williams <dcbw@redhat.com>, Pavel Roskin <proski@gnu.org>
Subject: Re: [PATCH] Update in-kernel orinoco drivers to upstream current CVS
Date: Sun, 4 Jul 2004 12:13:04 +1000 [thread overview]
Message-ID: <20040704021304.GD25992@zax> (raw)
In-Reply-To: <20040703010709.A22334@electric-eye.fr.zoreil.com>
On Sat, Jul 03, 2004 at 01:07:09AM +0200, Francois Romieu wrote:
> Jean Tourrilhes <jt@bougret.hpl.hp.com> :
> [...]
> > The difference between 0.13e and 0.15rc1+ is not small. I
> > believe Pavel did a good job in splitting the various patches in small
> > pieces when adding them to the CVS, and David has tracked the kernel,
> > but reconciliating the two branches is no trivial matter.
>
> I have extracted a few things from the bz2 ball that Dan sent (against
> 2.6.7-mm5 which already contains some orinoco bits):
>
> -rw-r--r-- 1 romieu users 4564 jui 3 00:47 orinoco-10.patch
> -rw-r--r-- 1 romieu users 15999 jui 3 00:47 orinoco-20.patch
> -rw-r--r-- 1 romieu users 33135 jui 3 00:47 orinoco-30.patch
> -rw-r--r-- 1 romieu users 11463 jui 3 00:47 orinoco-40.patch
>
> Available at http://www.fr.zoreil.com/linux/kernel/2.6.x/2.6.7-mm5/
>
> So far the patches lack comments but they are quite simple.
Aha, that's a good start. During the week I'll try to look at these,
put my rubber stamp on them, and send them on to Jeff.
One thing I notice though (from your later ones, actually) is that you
seem to be moving from current 2.6 to the CVS HEAD branch. That
includes the orinoco_usb stuff, which I still don't think is done
right and would rather not push. I know this is asking a bir of a
favour, given how useless I've been at doing the update myself, but
your patches would be much more useful if they aimed at the CVS
"for_linus" branch.
--
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
next prev parent reply other threads:[~2004-07-04 2:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 22:26 [PATCH] Update in-kernel orinoco drivers to upstream current CVS 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 [this message]
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-09 18:53 ` [PATCH] Updated pci-skeleton.c Pavel Roskin
2004-07-09 19:18 ` Jeff Garzik
2004-07-08 23:17 ` [PATCH] Update in-kernel orinoco drivers to upstream current CVS Francois Romieu
2004-07-08 23:30 ` Jeff Garzik
2004-07-03 6:08 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-07-02 19:11 Dan Williams
2004-07-02 19:25 ` Jeff Garzik
2004-07-04 2:01 ` David Gibson
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=20040704021304.GD25992@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