linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Mohammed Shafi <mshajakhan@atheros.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Luis Rodriguez <Luis.Rodriguez@Atheros.com>
Subject: Re: [PATCH] ath9k: make use of slot time macros
Date: Mon, 14 Feb 2011 14:48:05 +0100	[thread overview]
Message-ID: <4D593295.6060800@openwrt.org> (raw)
In-Reply-To: <4D58B39B.9040207@atheros.com>

On 2011-02-14 5:46 AM, Mohammed Shafi wrote:
> On Monday 14 February 2011 10:11 AM, Mohammed Shafi wrote:
>> On Friday 11 February 2011 09:59 PM, John W. Linville wrote:
>>> On Fri, Feb 11, 2011 at 05:21:06PM +0100, Felix Fietkau wrote:
>>>> On 2011-02-11 5:15 PM, John W. Linville wrote:
>>>>> On Fri, Feb 11, 2011 at 01:52:23PM +0100, Felix Fietkau wrote:
>>>>>> On 2011-02-11 8:01 AM, Mohammed Shafi Shajakhan wrote:
>>>>>>> From: Mohammed Shafi Shajakhan<mshajakhan@atheros.com>
>>>>>>>
>>>>>>> Instead of using raw numbers to assign slot time it would be 
>>>>>>> better to
>>>>>>> make use of predefined slot time macros
>>>>>> How does this make it better?
>>>>> Maybe if it was ATH9K_SHORT_SLOT_TIME it would make more sense?
>>>> Well, neither the unit of this variable, nor the values that can be 
>>>> used
>>>> are ath9k specific.
> Felix  then I don't know why these macros are used here and I followed 
> the same thing:
> 
> htc_drv_beacon.c 242 if (ah->slottime == ATH9K_SLOT_TIME_20)
> init.c           517 sc->beacon.slottime = ATH9K_SLOT_TIME_9;
Just because the macros are there doesn't mean that it was a good idea
to use them. As far as I know, these were simply inherited from the
Atheros codebase that ath9k was based on.
I actually consider the code more readable without the redundant
"ATH9K_SLOT_TIME_" part.

- Felix

  reply	other threads:[~2011-02-14 14:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11  7:01 [PATCH] ath9k: make use of slot time macros Mohammed Shafi Shajakhan
2011-02-11 12:52 ` Felix Fietkau
2011-02-11 16:15   ` John W. Linville
2011-02-11 16:21     ` Felix Fietkau
2011-02-11 16:29       ` John W. Linville
2011-02-14  4:41         ` Mohammed Shafi
2011-02-14  4:46           ` Mohammed Shafi
2011-02-14 13:48             ` Felix Fietkau [this message]
2011-02-14 14:02               ` Mohammed Shafi
2011-02-14 14:29                 ` Felix Fietkau
2011-02-14 14:36                   ` Mohammed Shafi
2011-02-14 20:14           ` John W. Linville
2011-02-15  6:07             ` Mohammed Shafi
2011-02-14  4:35     ` Mohammed Shafi
2011-02-14  4:31   ` Mohammed Shafi

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=4D593295.6060800@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mshajakhan@atheros.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;
as well as URLs for NNTP newsgroup(s).