From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: "Joshua M. Kwan" <joshk@ludicrus.ath.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Wireless Extensions v16-3 - clean patches
Date: Thu, 9 Jan 2003 10:13:41 -0800 [thread overview]
Message-ID: <20030109181340.GB24023@bougret.hpl.hp.com> (raw)
In-Reply-To: <20030109043119.GA13910@kanoe.ludicrus.net>
On Wed, Jan 08, 2003 at 08:31:19PM -0800, Joshua M. Kwan wrote:
> Hi Jean,
>
> I have attached two patches that allow current 2.5.54 BK and 2.4.20
> vanilla to patch cleanly from whatever WE they came with to WE16,
> from your site. This is easier since the patches on your website for
> 2.4.20 require two patches, and the 2.5.x one has a single reject
> that was not hard to resolve (just a few line breaks here and there
> and editing of the surrounding text confused patch.)
>
> For 2.5, the BK i diffed against was a fresh tree from today, but
> since you're the one that makes all the changes to those files
> anyway, it really doesn't matter until a new WE is pushed! And then
> this patch won't be necessary at all :)
>
> Both patches should be placed in the root of the source tree and
> applied with -p0.
>
> Hope this can benefit others who would like to easily upgrade their
> WE :)
>
> Regards
> Josh
Thanks for the good work !
For 2.4.X : 2.4.21-pre2 has WE-15, so if you get it it's only
one patch (the one on my page).
For 2.5.X : my Pcmcia cards still don't work with 2.5.54, so
I'm currently no too worried about 2.5.X at the moment.
Also, the current WE16-3 may not be the final version, as I'm
waiting for feedback from driver authors. Talking of feedback, which
part of WE16 do you need and why ?
Have fun...
Jean
next prev parent reply other threads:[~2003-01-09 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 4:31 Joshua M. Kwan
2003-01-09 18:13 ` Jean Tourrilhes [this message]
2003-01-09 19:33 ` Joshua M. Kwan
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=20030109181340.GB24023@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=joshk@ludicrus.ath.cx \
--cc=jt@hpl.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®