From: Kalle Valo <kvalo@codeaurora.org>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH v2] ath9k: spectral - simplify max_index calculation
Date: Mon, 20 Jul 2015 18:48:08 +0300 [thread overview]
Message-ID: <877fpusudj.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5582E0CF.1050804@neratec.com> (Zefir Kurtisi's message of "Thu, 18 Jun 2015 17:16:31 +0200")
Zefir Kurtisi <zefir.kurtisi@neratec.com> writes:
> After further discussion with Nick, we better leave spectral as is.
>
> Please ignore / drop this one.
Ok, patch dropped.
> On 06/18/2015 01:17 PM, Zefir Kurtisi wrote:
>> The max_index value provided in the spectral data set
>> has to be interpreted differently for HT20 and HT40.
>> In HT40, the value is given as unsigned index and
>> shall be taken as is, while in HT20 it is a signed
>> value around bin index 28 and needs to be converted
>> to an unsigned index.
>>
>> This patch simplifies the previous correction and
>> prepares the related functions to be shared with
>> the DFS module.
>>
>> Signed-off-by: Zefir Kurtisi <zefir.kurtisi@neratec.com>
Please edit your quotes, leaving this extra cruft makes it hard for me
to use patchwork.
--
Kalle Valo
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Zefir Kurtisi <zefir.kurtisi@neratec.com>
Cc: linux-wireless@vger.kernel.org, mickflemm@gmail.com,
ath9k-devel@venema.h4ckr.net
Subject: Re: [PATCH v2] ath9k: spectral - simplify max_index calculation
Date: Mon, 20 Jul 2015 18:48:08 +0300 [thread overview]
Message-ID: <877fpusudj.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <5582E0CF.1050804@neratec.com> (Zefir Kurtisi's message of "Thu, 18 Jun 2015 17:16:31 +0200")
Zefir Kurtisi <zefir.kurtisi@neratec.com> writes:
> After further discussion with Nick, we better leave spectral as is.
>
> Please ignore / drop this one.
Ok, patch dropped.
> On 06/18/2015 01:17 PM, Zefir Kurtisi wrote:
>> The max_index value provided in the spectral data set
>> has to be interpreted differently for HT20 and HT40.
>> In HT40, the value is given as unsigned index and
>> shall be taken as is, while in HT20 it is a signed
>> value around bin index 28 and needs to be converted
>> to an unsigned index.
>>
>> This patch simplifies the previous correction and
>> prepares the related functions to be shared with
>> the DFS module.
>>
>> Signed-off-by: Zefir Kurtisi <zefir.kurtisi@neratec.com>
Please edit your quotes, leaving this extra cruft makes it hard for me
to use patchwork.
--
Kalle Valo
next prev parent reply other threads:[~2015-07-20 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 11:17 [ath9k-devel] [PATCH v2] ath9k: spectral - simplify max_index calculation Zefir Kurtisi
2015-06-18 11:17 ` Zefir Kurtisi
2015-06-18 15:16 ` [ath9k-devel] " Zefir Kurtisi
2015-06-18 15:16 ` Zefir Kurtisi
2015-07-20 15:48 ` Kalle Valo [this message]
2015-07-20 15:48 ` Kalle Valo
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=877fpusudj.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath9k-devel@lists.ath9k.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.