From: Richard Farina <sidhayn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Renzmann <mrenzmann@madwifi-project.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Fwd: please don't regress ath5k.h]
Date: Mon, 24 Nov 2008 10:29:52 -0500 [thread overview]
Message-ID: <492AC870.3030103@gmail.com> (raw)
In-Reply-To: <1227507381.3599.55.camel@johannes.berg>
Johannes Berg wrote:
> On Mon, 2008-11-24 at 06:44 +0100, Michael Renzmann wrote:
>
>> Hi.
>>
>> Richard Farina wrote:
>>
>>> I recently saw this additional comment added to wireless-testing.git and
>>> it has me a bit concerned. I use this feature for a specific patch set
>>> that I maintain and it would break it pretty bad to remove this.
>>>
>> Just an idea: what prevents you to add a patch to that patchset that
>> reenables the amount of code you require from the CHAN_DEBUG stuff should
>> it be removed upstream?
>>
>
> Seconded, upstream should remove all the junk that it doesn't directly
> need.
>
> johannes
>
I actually don't have a problem with removing chan_debug, I was merely
requesting that the size hack it enables not be removed.
More specifically in base.h I believe the code I specifically require is:
#if CHAN_DEBUG
#define ATH_CHAN_MAX (26+26+26+200+200)
#else
#define ATH_CHAN_MAX (14+14+14+252+20)
#endif
When removing chan_debug just please leave the higher max. To be honest
I don't know for sure what this code means but since enabling it fixes
my patch it is clearly required. There is no reason to be removing this
as I am hoping to push a few patches upstream to properly support the
capabilities of the hardware.
Thanks,
Rick
next prev parent reply other threads:[~2008-11-24 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 2:42 [Fwd: please don't regress ath5k.h] Richard Farina
2008-11-24 5:44 ` Michael Renzmann
2008-11-24 6:16 ` Johannes Berg
2008-11-24 15:29 ` Richard Farina [this message]
2008-11-24 18:29 ` Jouni Malinen
2008-11-24 18:39 ` Richard Farina
2008-11-24 21:35 ` Luis R. Rodriguez
2008-11-24 22:21 ` Richard Farina
2008-11-24 23:01 ` Luis R. Rodriguez
2008-11-24 20:25 ` Nick Kossifidis
2008-11-24 20:51 ` Richard Farina
2008-11-24 20:52 ` Nick Kossifidis
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=492AC870.3030103@gmail.com \
--to=sidhayn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mrenzmann@madwifi-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.