From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kalle Valo Date: Mon, 20 Jul 2015 18:48:08 +0300 Subject: [ath9k-devel] [PATCH v2] ath9k: spectral - simplify max_index calculation In-Reply-To: <5582E0CF.1050804@neratec.com> (Zefir Kurtisi's message of "Thu, 18 Jun 2015 17:16:31 +0200") References: <1434626241-1334-1-git-send-email-zefir.kurtisi@neratec.com> <5582E0CF.1050804@neratec.com> Message-ID: <877fpusudj.fsf@kamboji.qca.qualcomm.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Zefir Kurtisi 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 Please edit your quotes, leaving this extra cruft makes it hard for me to use patchwork. -- Kalle Valo