From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: selvam <sathakselva@gmail.com>
Cc: "ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Vipin M <vipintm@gmail.com>
Subject: Re: [ath9k-devel] [RFC] ath9k: 4ms frame length table update
Date: Thu, 18 Mar 2010 09:00:34 -0700 [thread overview]
Message-ID: <20100318160034.GC2269@tux> (raw)
In-Reply-To: <1aee2dca1003172337g5d66a03ex20ebab74707a6c56@mail.gmail.com>
On Wed, Mar 17, 2010 at 11:37:29PM -0700, selvam wrote:
> Hi,
>
> The 4 ms frame length table is updated to support up to MCS 31.
>
> These values are calculated based on the equation 9.1 from the IEEE 802.11n standard.
> These values are rounded off to multiple of 4 bytes. If the final value is greater than 65535 then it is changed to 65532, since the maximum A-MPDU length is 65535 bytes.
Thanks for this patch, but can you elaborate on what your patch does other
than the above. For example, you may want to mention that although the current
ath9k driver does not support up to MCS31 your patch would enable such support
for future chipsets which could be supported. You also forgot to Signed-off-by
it, and provide a clearer commit log entry. Check git log for examples on
wireless-testing, also read:
http://wireless.kernel.org/en/developers/Documentation/SubmittingPatches
http://wireless.kernel.org/en/developers/Documentation
Luis
next parent reply other threads:[~2010-03-18 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1aee2dca1003172337g5d66a03ex20ebab74707a6c56@mail.gmail.com>
2010-03-18 16:00 ` Luis R. Rodriguez [this message]
2010-03-18 16:53 ` [ath9k-devel] [RFC] ath9k: 4ms frame length table update Vasanthakumar Thiagarajan
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=20100318160034.GC2269@tux \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sathakselva@gmail.com \
--cc=vipintm@gmail.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).