Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp315444pxb; Thu, 26 Aug 2021 03:59:32 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwwX/mYQDkt2nGic36WtOErcTcwfxYltzTtiu5cehwMYkTXSoQ6r30unlfTAowNX+MhvyDq X-Received: by 2002:a92:cb52:: with SMTP id f18mr2427422ilq.120.1629975572430; Thu, 26 Aug 2021 03:59:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1629975572; cv=none; d=google.com; s=arc-20160816; b=CjN2bFzSUzIVsmBqY4byfDtQqrfBQla8rzrSCEh2LLYzJd8GAS7PpeCBeR6oaJb3Zs zvObvv2gQeHFKSG1sHz08niofVIkF5cf0KrT+7QAqX1gjpw1P2XNQoCUpG6BTwbnkiRk tCDguAVUq9NQSfhvYPVCGe6YzP752ASHzTgCHr0sr/6IgtZmcbW1Gt4FBuIwj73jPfwG Lu2gElxCALMVcXwnl7askrbnED0lh9nNt7/IOG7wzHgkJ/ZgHohE7SOQGbRR8E4zsUM6 1bp0VMqWG6ELEnmjxZGGpPPYQbxr/a3bl2oyDSbAgR8/1B57rIjYfAyiRXj1dCpSUikg 6Ofg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=gDiGKjEUkKRAhz5HdTK51/IAOIhHO1MVRogdEKMpohQ=; b=PtRsPxFvjlEagxvo3qAiHWWWwr9Vy1QU2lnLf33exOPNsXIjaclfYKMRZmy/V2rGTZ zvyVUOU8s17UzTpPx0XTs5vl+kwZoBBuluIwdX2ZevU033lLJCbpZLDm4VOo9TtJDNJ/ jktgNH4fV8boctHyPZHrNbX9Yzf/L3epKDPQGTqh6EBNEFhrqd2KY0t8D9q0ZuBA2wS4 a6G2e0xrBaPjIQowV2Vq8hv2Rxr5ONNgwchseZpFvTANxw20AmmUUbSPOUvMOHn7xwd0 /YZHnhr8BFlu5leS+M4ZsA32N/jEDJlEBdUuQk0ayzJF68SbtS8ipxZHMMLYo88vC/jY AgdQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=fXridZ37; 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; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f10si2352021ilk.8.2021.08.26.03.59.21; Thu, 26 Aug 2021 03:59:32 -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; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=fXridZ37; 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; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241634AbhHZLAC (ORCPT + 99 others); Thu, 26 Aug 2021 07:00:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38506 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231485AbhHZLAB (ORCPT ); Thu, 26 Aug 2021 07:00:01 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 83F6BC061757 for ; Thu, 26 Aug 2021 03:59:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=Content-Transfer-Encoding:MIME-Version: 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=gDiGKjEUkKRAhz5HdTK51/IAOIhHO1MVRogdEKMpohQ=; t=1629975554; x=1631185154; b=fXridZ37kkzpjiOm4vEIiJ9kWg8B6RyVB9olaUoP3NzsFjC 7QFEPVoyI3wJaoOA9T4B3ZmVv1afErjnXkuWXfguPCmg/26r1iN8DLNEi9MZf22vejPOd75wPn6OM MCVyHkp4NP93P2lIeoUYAGsojO3YHQgxYLYJxsTSvIvuNAEIFbY0pMY1oWGQSBZIe5kUCR1FguE/Z PtZ6AHafXty12LkrwveNSuJtjQ5+5vTlQGDg4eOKBESdKZa8U+8vo+CPsz1WcwURCjZf2NYSiVo/J KMfOFdWlTetY8sA1saSM1TDjdt6oGA+2awMjW+hmYODA6HtRCeHo+XIfUzRNj/JQ==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.94.2) (envelope-from ) id 1mJD6E-00G7PG-3A; Thu, 26 Aug 2021 12:59:10 +0200 Message-ID: <7e07a64f33bc1a1ca09e36d6152628478a622b69.camel@sipsolutions.net> Subject: Re: [PATCH v2 1/8] cfg80211: add power type definition for 6 GHz From: Johannes Berg To: Wen Gong Cc: ath11k@lists.infradead.org, linux-wireless@vger.kernel.org Date: Thu, 26 Aug 2021 12:59:09 +0200 In-Reply-To: References: <20210820122041.12157-1-wgong@codeaurora.org> <20210820122041.12157-2-wgong@codeaurora.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-malware-bazaar: not-scanned Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Thu, 2021-08-26 at 18:57 +0800, Wen Gong wrote: > On 2021-08-26 16:20, Johannes Berg wrote: > > >  struct cfg80211_chan_def { > > >   struct ieee80211_channel *chan; > > > @@ -684,6 +685,7 @@ struct cfg80211_chan_def { > > >   u32 center_freq2; > > >   struct ieee80211_edmg edmg; > > >   u16 freq1_offset; > > > + enum nl80211_ap_reg_power power_type; > > > > I'm not sure why this should be in the chandef, there's no way that > > anything in cfg80211 is ever using it there, at least in your patches. > > > It is used in mac80211 of [PATCH v2 3/8] mac80211: add parse regulatory > info in 6 GHz operation information. > should i move it to mac80211's .h file? > > > +/** > > > + * enum nl80211_ap_reg_power - regulatory power for a Access Point [...] > > > It is used in mac80211 of [PATCH v2 3/8] mac80211: add parse regulatory > info in 6 GHz operation information. > should i move it to mac80211's .h file? Yeah I saw both of them are used, but why are they defined as nl80211 API? Do you have any intention to set them through nl80211? And like I said, I'm not really convinced this belongs into struct cfg80211_chan_def either. Maybe it should be in bss_conf too? johannes >