Linux wireless drivers development
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: gregory.greenman@intel.com
Cc: johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] wifi: iwlwifi: mvm: fix the order of TIMING_MEASUREMENT notifications
Date: Mon, 10 Apr 2023 09:28:14 -0700	[thread overview]
Message-ID: <20230410162814.GA2775@dev-arch.thelio-3990X> (raw)
In-Reply-To: <20230410140721.897683-1-gregory.greenman@intel.com>

On Mon, Apr 10, 2023 at 05:07:20PM +0300, gregory.greenman@intel.com wrote:
> From: Gregory Greenman <gregory.greenman@intel.com>
> 
> Host commands and notifications are expected to be ordered in
> iwl_mvm_groups array. Fix the order of two new TIMING_MEASUREMENT
> notifications.
> 
> Fixes: c7eca79def44 ("wifi: iwlwifi: mvm: report hardware timestamps in RX/TX status")
> Reported-by: Nathan Chancellor <nathan@kernel.org>
> Link: https://lore.kernel.org/linux-wireless/20230331175121.GA3127046@dev-arch.thelio-3990X/
> Signed-off-by: Gregory Greenman <gregory.greenman@intel.com>

Thanks for the quick fix! It appears to work for me.

Tested-by: Nathan Chancellor <nathan@kernel.org>

> ---
>  drivers/net/wireless/intel/iwlwifi/mvm/ops.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/ops.c b/drivers/net/wireless/intel/iwlwifi/mvm/ops.c
> index 56a4e9d6ae33..6f082059025a 100644
> --- a/drivers/net/wireless/intel/iwlwifi/mvm/ops.c
> +++ b/drivers/net/wireless/intel/iwlwifi/mvm/ops.c
> @@ -472,8 +472,8 @@ static const struct iwl_hcmd_names iwl_mvm_legacy_names[] = {
>  	HCMD_NAME(SCAN_OFFLOAD_PROFILES_QUERY_CMD),
>  	HCMD_NAME(BT_COEX_UPDATE_REDUCED_TXP),
>  	HCMD_NAME(BT_COEX_CI),
> -	HCMD_NAME(WNM_80211V_TIMING_MEASUREMENT_CONFIRM_NOTIFICATION),
>  	HCMD_NAME(WNM_80211V_TIMING_MEASUREMENT_NOTIFICATION),
> +	HCMD_NAME(WNM_80211V_TIMING_MEASUREMENT_CONFIRM_NOTIFICATION),
>  	HCMD_NAME(PHY_CONFIGURATION_CMD),
>  	HCMD_NAME(CALIB_RES_NOTIF_PHY_DB),
>  	HCMD_NAME(PHY_DB_CMD),
> -- 
> 2.38.1
> 

      parent reply	other threads:[~2023-04-10 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 14:07 [PATCH 1/2] wifi: iwlwifi: mvm: fix the order of TIMING_MEASUREMENT notifications gregory.greenman
2023-04-10 14:07 ` [PATCH 2/2] wifi: iwlwifi: fix duplicate entry in iwl_dev_info_table gregory.greenman
2023-04-10 16:28 ` Nathan Chancellor [this message]

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=20230410162814.GA2775@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=gregory.greenman@intel.com \
    --cc=johannes@sipsolutions.net \
    --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