From: Luca Coelho <luca@coelho.fi>
To: Luca Coelho <luca@coelho.fi>
Cc: kvalo@codeaurora.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 01/12] iwlwifi: mvm: add support for range request command version 13
Date: Thu, 26 Aug 2021 23:38:51 +0300 [thread overview]
Message-ID: <E1mJM9C-002XND-M2@farmhouse.coelho.fi> (raw)
In-Reply-To: <iwlwifi.20210826224715.9dcd5210b7e5.I76f6977cde852de0f251344e279ad85076eef8d6@changeid>
Luca Coelho <luca@coelho.fi> wrote:
> From: Avraham Stern <avraham.stern@intel.com>
>
> This version adds the following configuration options:
> 1. Set the BSS color for NDP ranging
> 2. Set the minimum and maximum time between measurements for
> non trigger based NDP ranging.
> 3. Terminate the session in case the responder requests LMR feedback.
>
> Signed-off-by: Avraham Stern <avraham.stern@intel.com>
> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
12 patches applied to iwlwifi-next.git, thanks.
830aa3e7d1ca iwlwifi: mvm: add support for range request command version 13
bd34ff380e78 iwlwifi: mvm: add support for responder config command version 9
b05c1d14a177 iwlwifi: move get pnvm file name to a separate function
fb3fac5fafa8 iwlwifi: mvm: introduce iwl_stored_beacon_notif_v3
cde5dbaa35ed iwlwifi: mvm: support broadcast TWT alone
090f1be3abf3 iwlwifi: mvm: Fix scan channel flags settings
e257d969f365 iwlwifi: mvm: don't use FW key ID in beacon protection
765fdb17276a iwlwifi: export DHC framework and add first public entry, twt_setup
4956fe796656 iwlwifi: mvm: add fixed_rate debugfs entry to public DHC
610666bec1ea iwlwifi: Add support for getting rf id with blank otp
cc6358a93c3a iwlwifi: Add support for more BZ HWs
1b740380f5fa iwlwifi: Start scratch debug register for Bz family
next prev parent reply other threads:[~2021-08-26 20:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 19:47 [PATCH v2 00/12] iwlwifi: updates intended for v5.15 2021-08-20 v2 Luca Coelho
2021-08-26 19:47 ` [PATCH v2 01/12] iwlwifi: mvm: add support for range request command version 13 Luca Coelho
2021-08-26 20:38 ` Luca Coelho [this message]
2021-08-26 19:47 ` [PATCH v2 02/12] iwlwifi: mvm: add support for responder config command version 9 Luca Coelho
2021-08-26 19:47 ` [PATCH v2 03/12] iwlwifi: move get pnvm file name to a separate function Luca Coelho
2021-08-26 19:47 ` [PATCH v2 04/12] iwlwifi: mvm: introduce iwl_stored_beacon_notif_v3 Luca Coelho
2021-08-26 19:47 ` [PATCH v2 05/12] iwlwifi: mvm: support broadcast TWT alone Luca Coelho
2021-08-26 19:47 ` [PATCH v2 06/12] iwlwifi: mvm: Fix scan channel flags settings Luca Coelho
2021-08-26 19:47 ` [PATCH v2 07/12] iwlwifi: mvm: don't use FW key ID in beacon protection Luca Coelho
2021-08-26 19:47 ` [PATCH v2 08/12] iwlwifi: export DHC framework and add first public entry, twt_setup Luca Coelho
2021-08-26 19:47 ` [PATCH v2 09/12] iwlwifi: mvm: add fixed_rate debugfs entry to public DHC Luca Coelho
2021-08-26 19:47 ` [PATCH v2 10/12] iwlwifi: Add support for getting rf id with blank otp Luca Coelho
2021-10-22 6:25 ` Luca Coelho
2021-10-22 7:13 ` Luca Coelho
2021-10-22 7:41 ` Luca Coelho
2021-08-26 19:47 ` [PATCH v2 11/12] iwlwifi: Add support for more BZ HWs Luca Coelho
2021-08-26 19:47 ` [PATCH v2 12/12] iwlwifi: Start scratch debug register for Bz family Luca Coelho
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=E1mJM9C-002XND-M2@farmhouse.coelho.fi \
--to=luca@coelho.fi \
--cc=kvalo@codeaurora.org \
--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 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).