Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Message-ID: <a2fe2cad3c93ae8516568b6a8f5395dae6d9ba30.camel@sipsolutions.net>
Subject: Re: [RFC 6/7] nl80211: add KHz frequency offset for most wifi
 commands
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Thomas Pedersen <thomas@adapt-ip.com>
Cc:     linux-wireless <linux-wireless@vger.kernel.org>
Date:   Wed, 01 Apr 2020 09:10:06 +0200
In-Reply-To: <20200401062150.3324-7-thomas@adapt-ip.com>
References: <20200401062150.3324-1-thomas@adapt-ip.com>
         <20200401062150.3324-7-thomas@adapt-ip.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

On Tue, 2020-03-31 at 23:21 -0700, Thomas Pedersen wrote:
> 
> TODO: several of these commands will eventually just
> ignore the _OFFSET component, like _JOIN_MESH,
> _CMD_RADAR_DETECT, etc. Should return an error to give
> user a hint things won't work as expected?

Wouldn't most of them already require that a channel with the given
frequency exists, and thus fail anyway?

johannes