Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp1996084ybg; Thu, 30 Jul 2020 07:55:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzohW13DGwIQt4zp0YElGCH7+8XTxfzBIfOGYGWwg9J+7UcgoMOxZCisNxXV+1W94KnsmW1 X-Received: by 2002:a17:906:4f0f:: with SMTP id t15mr2848229eju.337.1596120939071; Thu, 30 Jul 2020 07:55:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596120939; cv=none; d=google.com; s=arc-20160816; b=h//cquGEw1yonz18INx7geTv0ryYI/HZQS6Uzc/PO3Ae4ymS9mkgsdkxG7Y9AZ3rZt UfUus3vTI2MxaJHQfdJaOW0+rOuPVr0tIWVA+iW/3kP2xDORufH264CbqQLgbq41m1Sn tE5t/u9M40dl388Tbm/SOMaEeggOthy3zSIrTxlmTyt3niT1gGAN9XY6u40U5TFCvcEr 4zTu86ViWLl8Mw3hGc+cq3xtHH3P0s1j3HU+/rhR8ZEqSOePS621vnDLvH4uubkbquSM zMIXpg1EnWvsOd5GZbOa1t972wkg95kbrbjl9/7gpEhWyQOdVULBe0qRoTruKxXbES9Z 3Weg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=KyiHmCdZa23u4pQpONnVEbQqlbS0gH2yeVdzk/zSLL4=; b=UWz5e+dT1R0Fq24BlzOXBNx3k/TTvfvZctvXIS8gnfMChG50xmhLtExYCExdA5u/Sj rqyUgys8c2GR/cSHShXlr3T7nZQO/KHDj1+6yw9jgrMzdTaXQkWzlVCVwh7QvVO1BsHs XenfxxhxvBBsLvg6KbMz7DTccyolOTqoPUa4P7/pLl17E5L0pdivPF+8jBSCnCdI/BNY wYpsIRsi+cB6g1szfHjSDi9GpvqdFAMw5X365QK4fuS7pzWesSNV3/AdSXMasc8Ruf7O IXUTgjCd7sEsG3eMDCOmFsRTqTKQmYe7MgB5l7iI/afnoSuVEBe3ETRChP+FPkXnaHK4 /L0w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i2si3353755edu.549.2020.07.30.07.55.15; Thu, 30 Jul 2020 07:55:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726535AbgG3OzG (ORCPT + 99 others); Thu, 30 Jul 2020 10:55:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59198 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726275AbgG3OzG (ORCPT ); Thu, 30 Jul 2020 10:55:06 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0E12CC061574 for ; Thu, 30 Jul 2020 07:55:05 -0700 (PDT) Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.93) (envelope-from ) id 1k19xX-00DamX-8l; Thu, 30 Jul 2020 16:55:03 +0200 Message-ID: Subject: Re: [PATCH 3/4] nl80211: support SAE authentication offload in AP mode From: Johannes Berg To: Chi-Hsien Lin , linux-wireless@vger.kernel.org Cc: brcm80211-dev-list@broadcom.com, brcm80211-dev-list@cypress.com, Arend van Spriel , Franky Lin , Hante Meuleman , Wright Feng , Kalle Valo , Chung-Hsien Hsu Date: Thu, 30 Jul 2020 16:55:02 +0200 In-Reply-To: <20200623134938.39997-4-chi-hsien.lin@cypress.com> (sfid-20200623_155000_965089_06BEA254) References: <20200623134938.39997-1-chi-hsien.lin@cypress.com> <20200623134938.39997-4-chi-hsien.lin@cypress.com> (sfid-20200623_155000_965089_06BEA254) Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.4 (3.36.4-1.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Tue, 2020-06-23 at 08:49 -0500, Chi-Hsien Lin wrote: > From: Chung-Hsien Hsu > > Add support for SAE authentication offload in AP mode. It seems to me you need a new feature flag for this, just like in the PSK case, because brcmfmac in fact already sets this, and in fact as we can see in patch 4 it would now set it in two places depending on *different* firmware support conditions ... that may be OK for the firmware right now, but it still doesn't really make much sense. Please change to add another flag here. johannes