All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 4/8] ath10k: setup rx channel per ppdu
Date: Mon, 24 Mar 2014 10:56:14 +0200	[thread overview]
Message-ID: <87vbv46klt.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1395394341-3958-5-git-send-email-janusz.dziedzic@tieto.com> (Janusz Dziedzic's message of "Fri, 21 Mar 2014 10:32:17 +0100")

Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:

> Setup band and frequency in ieee80211_rx_status
> only once - for ppdu.
>
> Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>

[...]

> @@ -775,23 +794,7 @@ static void ath10k_process_rx(struct ath10k *ar, struct htt_rx_info *info)
>  	if (info->amsdu_more)
>  		status->flag |= RX_FLAG_AMSDU_MORE;
>  
> -	status->signal = info->signal;

What about the signal, how is it set now? I don't see that anywhere in
this patch.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 4/8] ath10k: setup rx channel per ppdu
Date: Mon, 24 Mar 2014 10:56:14 +0200	[thread overview]
Message-ID: <87vbv46klt.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1395394341-3958-5-git-send-email-janusz.dziedzic@tieto.com> (Janusz Dziedzic's message of "Fri, 21 Mar 2014 10:32:17 +0100")

Janusz Dziedzic <janusz.dziedzic@tieto.com> writes:

> Setup band and frequency in ieee80211_rx_status
> only once - for ppdu.
>
> Signed-off-by: Janusz Dziedzic <janusz.dziedzic@tieto.com>

[...]

> @@ -775,23 +794,7 @@ static void ath10k_process_rx(struct ath10k *ar, struct htt_rx_info *info)
>  	if (info->amsdu_more)
>  		status->flag |= RX_FLAG_AMSDU_MORE;
>  
> -	status->signal = info->signal;

What about the signal, how is it set now? I don't see that anywhere in
this patch.

-- 
Kalle Valo

  reply	other threads:[~2014-03-24  8:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21  9:32 [PATCH 0/8] ath10k: refactor htt_rx path Janusz Dziedzic
2014-03-21  9:32 ` Janusz Dziedzic
2014-03-21  9:32 ` [PATCH 1/8] ath10k: move rx related functions to htt_rx.c Janusz Dziedzic
2014-03-21  9:32   ` Janusz Dziedzic
2014-03-21  9:32 ` [PATCH 2/8] ath10k: rename process_rx_rates to ath10k_htt_rx_h_rates Janusz Dziedzic
2014-03-21  9:32   ` Janusz Dziedzic
2014-03-21  9:32 ` [PATCH 3/8] ath10k: introduce ieee80211_rx_status to htt_rx_info Janusz Dziedzic
2014-03-21  9:32   ` Janusz Dziedzic
2014-03-21  9:32 ` [PATCH 4/8] ath10k: setup rx channel per ppdu Janusz Dziedzic
2014-03-21  9:32   ` Janusz Dziedzic
2014-03-24  8:56   ` Kalle Valo [this message]
2014-03-24  8:56     ` Kalle Valo
2014-03-24 10:17     ` Janusz Dziedzic
2014-03-24 10:17       ` Janusz Dziedzic
2014-03-21  9:32 ` [PATCH 5/8] ath10k: kill not needed fields from htt_rx_info Janusz Dziedzic
2014-03-21  9:32   ` Janusz Dziedzic
2014-03-21  9:32 ` [PATCH 6/8] ath10k: return error when ath10k_htt_rx_amsdu_pop() fail Janusz Dziedzic
2014-03-21  9:32   ` Janusz Dziedzic
2014-03-21  9:32 ` [PATCH 7/8] ath10k: improve way we play with attention flags Janusz Dziedzic
2014-03-21  9:32   ` Janusz Dziedzic
2014-03-24  9:40   ` Kalle Valo
2014-03-24  9:40     ` Kalle Valo
2014-03-21  9:32 ` [PATCH 8/8] ath10k: finally kill htt_rx_info Janusz Dziedzic
2014-03-21  9:32   ` Janusz Dziedzic
2014-03-24  9:38   ` Kalle Valo
2014-03-24  9:38     ` 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=87vbv46klt.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=janusz.dziedzic@tieto.com \
    --cc=linux-wireless@vger.kernel.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.