From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E8149C4167B for ; Fri, 1 Dec 2023 10:18:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1378232AbjLAKRy (ORCPT ); Fri, 1 Dec 2023 05:17:54 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59824 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1378208AbjLAKRw (ORCPT ); Fri, 1 Dec 2023 05:17:52 -0500 Received: from mail11.truemail.it (mail11.truemail.it [IPv6:2001:4b7e:0:8::81]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 83472C7; Fri, 1 Dec 2023 02:17:58 -0800 (PST) Received: from francesco-nb.int.toradex.com (93-49-2-63.ip317.fastwebnet.it [93.49.2.63]) by mail11.truemail.it (Postfix) with ESMTPA id A9A7B20645; Fri, 1 Dec 2023 11:17:56 +0100 (CET) Date: Fri, 1 Dec 2023 11:17:55 +0100 From: Francesco Dolcini To: David Lin Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, briannorris@chromium.org, kvalo@kernel.org, francesco@dolcini.it, tsung-hsien.hsieh@nxp.com Subject: Re: [PATCH v7 03/12] wifi: mwifiex: fixed reassocation issue for WPA3. Message-ID: References: <20231128083115.613235-1-yu-hao.lin@nxp.com> <20231128083115.613235-4-yu-hao.lin@nxp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20231128083115.613235-4-yu-hao.lin@nxp.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 28, 2023 at 04:31:06PM +0800, David Lin wrote: > This issue is related to resatart/reconfigure AP. > > When AP is restarted or reconfigured, wpa_supplilcant will use cached > PMKSA to do association to AP. > Because association failure does not report to cfg80211/wpa_supplicant, > wpa_supplicant will always use cached PMKSA to do assocaiton. > Connection can't be established under this way. Same comment as patch 2, this seems a fixup of commit 1, you should fix that patch, not add a followup fixup commit. Francesco