Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp5395014pxb; Sun, 13 Feb 2022 19:53:27 -0800 (PST) X-Google-Smtp-Source: ABdhPJwVCdLWV9QNqTeyr2SubTc+YW7vQ1RSsDWRhuSpQAAjbqXS+08QDV6G0a4+m9eRSNFqYSkC X-Received: by 2002:a17:906:5356:: with SMTP id j22mr301381ejo.602.1644810807545; Sun, 13 Feb 2022 19:53:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1644810807; cv=none; d=google.com; s=arc-20160816; b=qNF7ix59ik9H9iatqfiXRBo1YLrWkdBjwAJ9A+9+gRMJmluShvQwa+YjsPd+J88GBG Aaur3H3ZafT5WRjnsGCFe1b02G811Xptidn39na5WSvCSYnIN9qgMj2JiTYKToHd9y5R FAiQvL2s7oNA2d5PGn8BzCL9WZtx6l/Usdjk3et8p/W8C930MZO/86qNiwHaB46vpTH5 ZtOk6VsHDh9y1EamE6f8evt456uFJQ+vkKfVNB7n+U74o+2cGvc+8YPBdVW3ZIHI8nzT e9bC3/9J9g2BhP9BTzC5b4QnXmo3DOrxVl3+/0pOw82wg/6QxJBrMY0YK4tO1esLDXtG pZzg== 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=PBtf4rPsa5e+Qn5Lx97LOIpX0MjdfeHnl6+s5vBIPaM=; b=AmE7wzBuIGl+JH99oQH7fFIKv6ARR2ZYzLon0nNpR+DUkXXyI/JplfDllty3i+UT3g 53RRXE+R8yWLQsS2DM1g9YuSv6+n9/KXHt00CtTj9JpAKzP3Vz8rlLDy0P8IZkoOKBIm cGCB9q1XVM5/GqT8ES0ebpMuSlBsNn+Uh3P+GqZNRux8N4Gz2L016jDNkGRRph/ICBks uf8zyVnh7MmodpqwByVDUuKLFVam6+1GXgrznye/nK37Df4jpgKFgVlcM6oXNLiJoyTw 1SXpZmN1TI7xYjG0U99zrPV1aG/g12GWCWK7UCZv+LQ3UZwSxQpN/iIj7W1yaza984G5 T9Qw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=iitebB+z; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hb16si10937278ejc.82.2022.02.13.19.53.02; Sun, 13 Feb 2022 19:53:27 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=iitebB+z; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S231478AbiBLVKR (ORCPT + 72 others); Sat, 12 Feb 2022 16:10:17 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:37622 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230000AbiBLVKR (ORCPT ); Sat, 12 Feb 2022 16:10:17 -0500 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E6FA0606F4 for ; Sat, 12 Feb 2022 13:10:12 -0800 (PST) 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=PBtf4rPsa5e+Qn5Lx97LOIpX0MjdfeHnl6+s5vBIPaM=; t=1644700213; x=1645909813; b=iitebB+zBhquD8KQoTIZuh8CGv+w8GTAZlkL4vWNZL07LPE 4dZWYuJrles+sW6jTAqJXNMTTCf+4lqS1HJ9TBCoYjpdrRCLuVsbhZD7ZmvoVw7mX4g8sUX0yeozp QNQAX0xqVYWOL6U7I+3yZP0PYsrl4whzjA91LnyxWicvVMFAI8H/ALRkqbIsjubcD1PscUTTD55RF PNzd4XlT8SJOEVPEdTKgxjE5vnh7ZGKU3Ggc3Igt++S6hDasqGQq6CJsH9RIXvS9BobxGbwNrAAs1 sC8MHPEw1RH8Ne3kmlvTRaTysXDMJiJVSE1PUwj3MaoN10iHnd94tooxWinRUP4Q==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.95) (envelope-from ) id 1nIzeh-000Mmp-3n; Sat, 12 Feb 2022 22:10:07 +0100 Message-ID: <6d87acca10648841b60e2a28a46a328340bf939a.camel@sipsolutions.net> Subject: Re: [PATCH 1/6] nl80211: vendor-cmd: qca: add command for CFR configuration From: Johannes Berg To: Venkateswara Naralasetty , ath11k@lists.infradead.org Cc: linux-wireless@vger.kernel.org Date: Sat, 12 Feb 2022 22:10:06 +0100 In-Reply-To: <1644592075-27082-2-git-send-email-quic_vnaralas@quicinc.com> References: <1644592075-27082-1-git-send-email-quic_vnaralas@quicinc.com> <1644592075-27082-2-git-send-email-quic_vnaralas@quicinc.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.3 (3.42.3-1.fc35) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-malware-bazaar: not-scanned X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, 2022-02-11 at 20:37 +0530, Venkateswara Naralasetty wrote: > This patch is to add vendor command support to configure per > peer CFR parameters. > That's pretty much the worst way to start this ... Please explain at least what CFR is? What does the feature do? And please also see https://wireless.wiki.kernel.org/en/developers/documentation/nl80211#vendor-specific_api johannes