linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: Loic Poulain <loic.poulain@linaro.org>,
	wcn36xx@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] wcn36xx: Correct band/freq reporting on RX
Date: Thu, 21 Oct 2021 08:44:27 +0300	[thread overview]
Message-ID: <8735ovextw.fsf@codeaurora.org> (raw)
In-Reply-To: <574368d8-ebfa-7765-ea0d-def99b855719@linaro.org> (Bryan O'Donoghue's message of "Wed, 20 Oct 2021 17:28:25 +0100")

Bryan O'Donoghue <bryan.odonoghue@linaro.org> writes:

> On 20/10/2021 14:54, Loic Poulain wrote:
>> Hi Bryan, Kalle,
>>
>> On Tue, 19 Oct 2021 at 02:26, Bryan O'Donoghue
>> <bryan.odonoghue@linaro.org> wrote:
>>>
>>> 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 :(
>>
>> So the missing channel 144 is due to a different problem, and is now fixed
>> in a subsequent patch:
>>      wcn36xx: Channel list update before hardware scan
>>
>> So I think we can go with this change :-).
>>
>> Regards,
>> Loic
>>
>
> Cool, nice job

I had already dropped this patch from my queue, but added it back now.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2021-10-21  5:44 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
2021-10-20 13:54     ` Loic Poulain
2021-10-20 16:28       ` Bryan O'Donoghue
2021-10-21  5:44         ` Kalle Valo [this message]
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=8735ovextw.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=bryan.odonoghue@linaro.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 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).