All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Loic Poulain <loic.poulain@linaro.org>, kvalo@codeaurora.org
Cc: wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] wcn36xx: Correct band/freq reporting on RX
Date: Tue, 19 Oct 2021 01:28:39 +0100	[thread overview]
Message-ID: <5a325d84-0d02-237b-a0a3-9eddd2e481de@linaro.org> (raw)
In-Reply-To: <d2128789-646f-1e02-0dd2-a9ac14b37cf7@linaro.org>

On 18/10/2021 23:51, Bryan O'Donoghue wrote:
> On 18/10/2021 11:57, Loic Poulain wrote:
>>           ieee80211_is_probe_resp(hdr->frame_control))
>>           status.boottime_ns = ktime_get_boottime_ns();
> 
> I think this is dangling in your tree, doesn't apply cleanly for me anyway
> 
> Other than that
> 
> Tested-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>

Hmm.

I'm told by a colleague with access to a router that has channel 144 - I 
do not BTW - that 144 is not showing up with the firmware offload scan.

We should probably hold off on applying for the time being :(

---
bod

  reply	other threads:[~2021-10-19  0:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 10:57 [PATCH 1/2] wcn36xx: Correct band/freq reporting on RX Loic Poulain
2021-10-18 10:57 ` [PATCH 2/2] wcn36xx: Enable hardware scan offload for 5Ghz band Loic Poulain
2021-10-18 22:51   ` Bryan O'Donoghue
2021-10-18 22:51 ` [PATCH 1/2] wcn36xx: Correct band/freq reporting on RX Bryan O'Donoghue
2021-10-19  0:28   ` Bryan O'Donoghue [this message]
2021-10-20 13:54     ` Loic Poulain
2021-10-20 16:28       ` Bryan O'Donoghue
2021-10-21  5:44         ` Kalle Valo
2021-10-27  7:41 ` 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=5a325d84-0d02-237b-a0a3-9eddd2e481de@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=wcn36xx@lists.infradead.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.