Received: by 2002:a05:7412:3b8b:b0:fc:a2b0:25d7 with SMTP id nd11csp2660945rdb; Mon, 12 Feb 2024 11:59:12 -0800 (PST) X-Forwarded-Encrypted: i=3; AJvYcCWGaSmoL6vQ2qylhcc/IPGdC3YAEV2QYMZq9Xzs9wUnTdxVCFiDDV4gv+XxqPMvDmSLuUHdFYT0fBsyVtYY3EF4GlqiEzm8dL8V3xvA4A== X-Google-Smtp-Source: AGHT+IFk5z7IH0SU2f/FRLB3wBVibqFJ9p3M9T7Eo5H/FHZ9wwRG19XXP2tzW0nOahykmqtrSbLO X-Received: by 2002:a05:6a21:394b:b0:19e:a520:105 with SMTP id ac11-20020a056a21394b00b0019ea5200105mr11415148pzc.34.1707767952718; Mon, 12 Feb 2024 11:59:12 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1707767952; cv=pass; d=google.com; s=arc-20160816; b=qY26Xx/0f9OrjZBMvEi8OBWOtms4ySP1zcwyNqRXHwLZ3XnFbydTmNI7bPmyPw+MwK FYzs2G8dWDdLHz+s8iGheq5+au3QZv+mHDMJrroIP3PdJuMlxf7ZI9qrysh6VyL/nzoB b8TOZNrTL477KPIFT1we2xpnV2dEcmF+VfvwNO7KcKE+eianTEi5rPbCOozMSmmBFjAk OElw+3PzpOKcisPf2BDeJkOjDuUExTdkqShQtgaYnB3RW5B2Y0qEvLSljpWgHa7zzv8H l4TFxTUjgPipsC4+N4IAR+++Cv6J7YI2va/niast46BQZVJULwS9upG8AY+Exqett3z6 iG+A== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:list-unsubscribe:list-subscribe:list-id:precedence :user-agent:content-transfer-encoding:references:in-reply-to:date:cc :to:from:subject:message-id:dkim-signature; bh=Lt5QOdxwmKP5wi+YgAc+nSKUxYGem+ulR+qGLgEENJ4=; fh=ePW/0sl80zgbs7BkZ5Ua/F4gn3yLGt+5y3A+SVknrDA=; b=hgPkRyn6X1MsDB+HPPKG8vHOOPDHvaM85Of4iWMKEghFSOMATnvrTdWi9Sdn5K/whi 2H1Gk5EuGCkpuGvBNHThhru0B/ShIQY3dwxOQ5CIqKWKPbgpGh2xKLj/y33NSzjKP2ZA TNxPc1e7tZfVCEaJOdiE6ZAVwIS2UZugfOGo2rIKsLqM5GB5go0L34m4GNB3XRqU5q7v TKcSRfnYeM3rXSu1WF52Q/Q44dlRovlqRjjt/oTaRJ/6WDHTlmKL0oKhEd/c0lnE/969 LZOdIiUFj1QpRqEpzw6YtAK6EftINBEIXizFtIRUNmcoGwKaHEK3FacxHY85ZPgOfthG 0TyA==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=nbYS1mTJ; arc=pass (i=1 spf=pass spfdomain=sipsolutions.net dkim=pass dkdomain=sipsolutions.net dmarc=pass fromdomain=sipsolutions.net); spf=pass (google.com: domain of linux-wireless+bounces-3484-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-wireless+bounces-3484-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net X-Forwarded-Encrypted: i=2; AJvYcCWMU03OiBTNnCiIoPlqtKY03wccjZfMA47lsCaLuTHGuy2PXbWH023m10mtQUUs9H/qwdyyrDDE2LT9MW1evcFBd5JJGPj5iiokyZN6ZA== Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id f4-20020a056a0022c400b006e050c011e8si1666472pfj.78.2024.02.12.11.59.12 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 12 Feb 2024 11:59:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless+bounces-3484-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=nbYS1mTJ; arc=pass (i=1 spf=pass spfdomain=sipsolutions.net dkim=pass dkdomain=sipsolutions.net dmarc=pass fromdomain=sipsolutions.net); spf=pass (google.com: domain of linux-wireless+bounces-3484-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-wireless+bounces-3484-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 60BF6284F4E for ; Mon, 12 Feb 2024 19:59:12 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id A3D6947F58; Mon, 12 Feb 2024 19:59:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="nbYS1mTJ" X-Original-To: linux-wireless@vger.kernel.org Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B6A7647A6F; Mon, 12 Feb 2024 19:59:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707767944; cv=none; b=N7IDWVK/GZ8eSqcMI429H+Av+MtopuCiCE9Vs9430RMoFXz7Zk4wzPjRtBnaQQq/oefjjk5dAcbBNZmUHz7pkkQAHTznIii/m4Mxz4mvpdxGGgjm0h4Uowh23FShhxUYW7pnN56T6Ziz1+fLuxQRYJCmecDFV9+tL8Ybq+i0xK8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707767944; c=relaxed/simple; bh=LAd7kAB0YVu3prmd6cMGizOB97wDW8LoD6QWTyinZjM=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=gOh2v1H1Wbhx4DsGSLyXfpBeQCslDg0taWRJEPakXQSaJCAmopGNz9MleLGo+lYScAuljiy9P8q1SeHKjYmvycdSXS5MofNjvhKY2tSJgpUjy6mMAEwX0w/YqGRaTTKzoUHRpvg5Wu8rOQ0xCOeCi2II6DpQjp0p7NjcUvrliHE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=nbYS1mTJ; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=Lt5QOdxwmKP5wi+YgAc+nSKUxYGem+ulR+qGLgEENJ4=; t=1707767941; x=1708977541; b=nbYS1mTJpuUZVVaAPrJ6hEoYhHw3wN+m5nsGwHEReM7zRvf I2kTARgwoStJkCr0zHZLotlBFFQ19ziV8zrJqVedsd47KBJh96Ieynd9BP0rqDxxtv2Z5OGNTa7id +8r+F7NgYdm8kO+QFASQXXmBs0glyZfcAEns13i4A3VQOl65YEHApnl2A5r0k8DMBN4TG2cfV1oJU g6twKQvNYoUooqbO0ShIHFlWZV5NNHpJzBNt6w0sEv8Q6/wirt1e1FR2hWM1VXl5FGwmax4CrQzwD pMx99UpuGJ1ksya4PmnbS64G4JM531Vz8wXBaMjnGXZxloe7En/LhAlOnshza1Eg==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.97) (envelope-from ) id 1rZcS5-00000006Taf-0gjr; Mon, 12 Feb 2024 20:58:53 +0100 Message-ID: <2c38eaed47808a076b6986412f92bb955b0599c3.camel@sipsolutions.net> Subject: Re: [PATCH 1/1] wifi: nl80211: Add support for plumbing SAE groups to driver From: Johannes Berg To: Kalle Valo , Vinayak Yadawad Cc: linux-wireless@vger.kernel.org, jithu.jance@broadcom.com, Arend van Spriel , netdev@vger.kernel.org, Jakub Kicinski Date: Mon, 12 Feb 2024 20:58:51 +0100 In-Reply-To: <87mss6f8jh.fsf@kernel.org> References: <309965e8ef4d220053ca7e6bd34393f892ea1bb8.1707486287.git.vinayak.yadawad@broadcom.com> <87mss6f8jh.fsf@kernel.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.50.3 (3.50.3-1.fc39) Precedence: bulk X-Mailing-List: linux-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Mon, 2024-02-12 at 09:25 +0200, Kalle Valo wrote: > What driver is going to use these new crypto settings? Or is this for an > out-of-tree driver? >=20 I'm sure it's for an out-of-tree driver. This is the _entirety_ of "@broadcom"'s wireless contributions with "--since=3D2020" (somewhat arbitrarily chosen, though going a bit further back has some "real" work in brcmfmac), as far as I can tell: Arend Van Spriel (1): cfg80211: adapt to new channelization of the 6GHz band Arend van Spriel (23): cfg80211: add VHT rate entries for MCS-10 and MCS-11 brcmfmac: use different error value for invalid ram base address brcmfmac: increase core revision column aligning core list brcmfmac: add xtlv support to firmware interface layer brcmfmac: support chipsets with different core enumeration space wifi: cfg80211: fix memory leak in query_regdb_file() wifi: brcmfmac: add function to unbind device to bus layer api wifi: brcmfmac: add firmware vendor info in driver info wifi: brcmfmac: add support for vendor-specific firmware api wifi: brcmfmac: add support for Cypress firmware api wifi: brcmfmac: add support Broadcom BCA firmware api wifi: brcmfmac: add vendor name in revinfo debugfs file wifi: brcmfmac: introduce BRCMFMAC exported symbols namespace wifi: brcmfmac: avoid handling disabled channels for survey dump wifi: brcmfmac: avoid NULL-deref in survey dump for 2G only device wifi: brcmfmac: fix regression for Broadcom PCIe wifi devices wifi: brcmfmac: change cfg80211_set_channel() name and signature wifi: brcmfmac: export firmware interface functions wifi: brcmfmac: add per-vendor feature detection callback wifi: brcmfmac: move feature overrides before feature_disable wifi: brcmfmac: avoid invalid list operation when vendor attach fails wifi: brcmfmac: allow per-vendor event handling wifi: brcmfmac: add linefeed at end of file Vinayak Yadawad (4): wifi: cfg80211: Allow P2P client interface to indicate port authoriza= tion cfg80211: Update Transition Disable policy during port authorization wifi: cfg80211: Allow AP/P2PGO to indicate port authorization to peer= STA/P2PClient wifi: nl80211: Extend del pmksa support for SAE and OWE security So looks to me like Broadcom doesn't want its (real) drivers to work in upstream, so I guess we really ought to just stop accommodating for them in the wireless stack... This only works if we collaborate, and I've said this before: I can't maintain something well that I cannot see (and possibly change) the user(s) of. I guess if Broadcom's plans change they can start by submitting drivers that actually use the relevant infrastructure. And note that I've said this to Qualcomm before: I don't really want to and can't (well) maintain a lot of stuff in the tree that exists there solely to make out-of-tree drivers happy. And @Broadcom: we really _want_ you to contribute upstream. But that shouldn't be dumping APIs over the wall when you need them and letting us sort out everything else ... johannes