Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4922921ybi; Tue, 28 May 2019 04:53:46 -0700 (PDT) X-Google-Smtp-Source: APXvYqx97y2UmxwpOFPBcXFGlDKS4Jpvsn53sI1ez+rwATfIdOZvjli3r/Ri+szKlik8OOgSD3Ss X-Received: by 2002:a63:1854:: with SMTP id 20mr129212559pgy.366.1559044426824; Tue, 28 May 2019 04:53:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559044426; cv=none; d=google.com; s=arc-20160816; b=dDwxcCieSLFGp85tJZCsitZgPbD0ihK1JXdUSgJbdTwqTQw4S9Or6KRnJXfXObIzup 4rzylCQGJyD6+8nnCKWYKaKs2m3waDozuzzckZEffNgXI0YfjGLVVbEeQ5lOz2VtqF6Z tnryEVS/IqaFDNPXw9Im5QTdzkbgW5gxw7JLXo0c0xxRuRV660I89DNFXm9ZvCln5KDu kyI12rxzc5ytrHd8UavuehtVfbjTDId/NieKXEpC48QFvElRNZxLJXzFV2a/FQMuCn0s CtuumXuUbzgQZKaRVTQR835E2s7FTVywvlS9qc5czII4ZMNzEqdYrvn1ulEBMFTZveG0 1Q7Q== 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 :date:to:from:subject:message-id; bh=728XJf76gH5NXilbWA5R3Pgm9Hj3H+0LDlI2eU0GipQ=; b=cOmCL+K1LCc0R41xvr3GVRN3sERnA6rynioQJGPJLgBfnOrOXlBS3dDVfTdhPwRtUl 7CXtHem4truI4HleXCMKaNmGbU9PzOSuYmhaYP0KS46B9BautTN8rvr40eCOHvkQWOKQ G3qAtp98x6S3qiLkuKLxoFKjz8uIJnXf82TJa/NPefUVyz9ZDKFbKG8eWnWyj8oixDre md31Kon0mchHZZ61eHiNUpyHY/H5XcV8QWUy0jk6u7jnHRT3UM6GQ2urkDD3e0YG9J1p fSCFJ4s5MjdepvbgIZRy0ppI7aKILdLAnVtr0EuQuYkmkhaJ2Dxme8xs4gyAVPQXo9xz PRJg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 71si7360847plf.156.2019.05.28.04.53.31; Tue, 28 May 2019 04:53:46 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726793AbfE1Lv7 (ORCPT + 99 others); Tue, 28 May 2019 07:51:59 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:48534 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726824AbfE1Lv7 (ORCPT ); Tue, 28 May 2019 07:51:59 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hVae6-0004HX-7R for linux-wireless@vger.kernel.org; Tue, 28 May 2019 13:51:58 +0200 Message-ID: Subject: FYI: vendor specific nl80211 API upstream From: Johannes Berg To: linux-wireless@vger.kernel.org Date: Tue, 28 May 2019 13:51:55 +0200 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-2.fc28) 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 Hi all, FYI - at the discussions in Prague we decided to let some vendor specific nl80211 API go upstream, and I've just documented the expected rules here: https://wireless.wiki.kernel.org/en/developers/documentation/nl80211#vendor-specific_api I guess this will be fine-tuned as we go along, but wanted all to be aware. johannes