From: Kalle Valo <kvalo@kernel.org>
To: Youghandhar Chintala <quic_youghand@quicinc.com>
Cc: <ath10k@lists.infradead.org>, <johannes@sipsolutions.net>,
<linux-wireless@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <quic_mpubbise@quicinc.com>
Subject: Re: [PATCH 0/2] Update the channel list if the change in channel flags
Date: Thu, 22 Dec 2022 16:00:50 +0200 [thread overview]
Message-ID: <87fsd7zgfh.fsf@kernel.org> (raw)
In-Reply-To: <20221222124221.30894-1-quic_youghand@quicinc.com> (Youghandhar Chintala's message of "Thu, 22 Dec 2022 18:12:19 +0530")
Youghandhar Chintala <quic_youghand@quicinc.com> writes:
> There are connection failures in hidden SSID case when the device is with
> default reg domain WW.
> For WW reg domain most of the 5 GHz channels are passive. When device
> listens to the beacon on that channel, the driver is updating its channel
> flag but firmware is not aware of it and firmware is not sending probes
> on that channels.
> Due to this, we are seeing connection failures when the device is tries to
> connect with hidden SSID AP.
> Whenever the driver detects a channel flag change, send the updated channel
> list command to the firmware.
>
> Youghandhae Chintala (2):
> wifi: cfg80211: Add beacon hint notifier support
> wifi: ath10k: update the channel list if change in channel flags.
If you submit patches again, please _always_ increase the version number
(ie. this one should be v2). Now there are two v1 patchsets and
difficult for maintainers to pick which one to take.
But don't resend the patchset just because of this. Hopefully this mail
makes it clear that this is v2.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
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@kernel.org>
To: Youghandhar Chintala <quic_youghand@quicinc.com>
Cc: <ath10k@lists.infradead.org>, <johannes@sipsolutions.net>,
<linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<quic_mpubbise@quicinc.com>
Subject: Re: [PATCH 0/2] Update the channel list if the change in channel flags
Date: Thu, 22 Dec 2022 16:00:50 +0200 [thread overview]
Message-ID: <87fsd7zgfh.fsf@kernel.org> (raw)
In-Reply-To: <20221222124221.30894-1-quic_youghand@quicinc.com> (Youghandhar Chintala's message of "Thu, 22 Dec 2022 18:12:19 +0530")
Youghandhar Chintala <quic_youghand@quicinc.com> writes:
> There are connection failures in hidden SSID case when the device is with
> default reg domain WW.
> For WW reg domain most of the 5 GHz channels are passive. When device
> listens to the beacon on that channel, the driver is updating its channel
> flag but firmware is not aware of it and firmware is not sending probes
> on that channels.
> Due to this, we are seeing connection failures when the device is tries to
> connect with hidden SSID AP.
> Whenever the driver detects a channel flag change, send the updated channel
> list command to the firmware.
>
> Youghandhae Chintala (2):
> wifi: cfg80211: Add beacon hint notifier support
> wifi: ath10k: update the channel list if change in channel flags.
If you submit patches again, please _always_ increase the version number
(ie. this one should be v2). Now there are two v1 patchsets and
difficult for maintainers to pick which one to take.
But don't resend the patchset just because of this. Hopefully this mail
makes it clear that this is v2.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-12-22 14:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 12:42 [PATCH 0/2] Update the channel list if the change in channel flags Youghandhar Chintala
2022-12-22 12:42 ` Youghandhar Chintala
2022-12-22 12:42 ` [PATCH 1/2] wifi: cfg80211: Add beacon hint notifier support Youghandhar Chintala
2022-12-22 12:42 ` Youghandhar Chintala
2023-01-18 16:30 ` Johannes Berg
2023-01-18 16:30 ` Johannes Berg
2023-02-15 11:26 ` Youghandhar Chintala (Temp)
2023-02-15 11:26 ` Youghandhar Chintala (Temp)
2023-02-15 15:10 ` Johannes Berg
2023-02-15 15:10 ` Johannes Berg
2023-02-22 0:22 ` Wen Gong
2023-02-22 0:22 ` Wen Gong
2023-02-22 8:00 ` Johannes Berg
2023-02-22 8:00 ` Johannes Berg
2022-12-22 12:42 ` [PATCH 2/2] wifi: ath10k: update the channel list if change in channel flags Youghandhar Chintala
2022-12-22 12:42 ` Youghandhar Chintala
2023-01-19 2:26 ` Wen Gong
2023-01-19 2:26 ` Wen Gong
2023-01-19 5:47 ` Youghandhar Chintala (Temp)
2023-01-19 5:47 ` Youghandhar Chintala (Temp)
2022-12-22 14:00 ` Kalle Valo [this message]
2022-12-22 14:00 ` [PATCH 0/2] Update the channel list if the " Kalle Valo
-- strict thread matches above, loose matches on Subject: below --
2022-12-22 12:05 Youghandhar Chintala
2022-12-22 12:05 ` Youghandhar Chintala
2022-12-22 12:40 ` Youghandhar Chintala (Temp)
2022-12-22 12:40 ` Youghandhar Chintala (Temp)
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=87fsd7zgfh.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_mpubbise@quicinc.com \
--cc=quic_youghand@quicinc.com \
/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.