From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: John Linville <linville@tuxdriver.com>,
netdev@vger.kernel.org, Bcm43xx-dev@lists.berlios.de,
Jean Tourrilhes <jt@hpl.hp.com>, Stefano Brivio <st3@riseup.net>
Subject: Re: [PATCH] WE-21 for bcm43xx (wireless-2.6 git)
Date: Thu, 31 Aug 2006 08:22:22 -0500 [thread overview]
Message-ID: <44F6E28E.2080807@lwfinger.net> (raw)
In-Reply-To: <200608311452.46166.mb@bu3sch.de>
Michael Buesch wrote:
> On Thursday 31 August 2006 02:57, Larry Finger wrote:
>>
>> +#if WIRELESS_EXT > 20
>> +#define IW_ESSID_FIX 0
>> +#else
>> +#define IW_ESSID_FIX 1
>> +#endif
>
> Eh, was this useless #if in the original patch I signed-off, too?
> Because I want to revert my sign-off. :)
> This #if is useless, because we always deal with only one single
> WE version in the kernel. #if WIRELESS_EXT will always be true.
> So remove this and also remove the other #if below.
>
Yes, it was. I saw this, but left it in because I cannot control the inclusion of the other patch
that brings the NET components up to WE-21, and it seemed that the behavior could be wrong if the
kernel were at WE-20. I'm quite certain that the patch will _NOT_ be included in 2.6.18 as it is
clearly not a bug fix. Once I see WE-21 in the kernel, I'll remove these #ifdef's and eliminate
IW_ESSID_FIX.
If I missed something, please let me know, and I'll resubmit the patch now.
John, have you merged, or do you plan to merge, "[PATCH 2.6.18] WE-21 support (core API)" into
wireless-2.6?
Larry
next prev parent reply other threads:[~2006-08-31 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 0:57 [PATCH] WE-21 for bcm43xx (wireless-2.6 git) Larry Finger
2006-08-31 12:52 ` Michael Buesch
2006-08-31 13:22 ` Larry Finger [this message]
[not found] ` <44F6E28E.2080807-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-08-31 13:57 ` John W. Linville
2006-08-31 16:44 ` Jean Tourrilhes
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=44F6E28E.2080807@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=jt@hpl.hp.com \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@vger.kernel.org \
--cc=st3@riseup.net \
/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).