Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2341087ybi; Thu, 20 Jun 2019 13:22:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqwhI+Munqzbp66qM5kBZFwKFMLuZqhJgae8tO6tFYmdPtHabU9Vt4zu6SyyCLeg/dwTPAC0 X-Received: by 2002:a63:8c0f:: with SMTP id m15mr2082721pgd.441.1561062133442; Thu, 20 Jun 2019 13:22:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561062133; cv=none; d=google.com; s=arc-20160816; b=MUnjBpk5jA0JVgye+1QNNJgNAQE5C65WMG8AlD6jaTtYW1o1Jnz9BtxLpiPhsf3cfW 5ZlbSzVKqM/SW6cZCeku4HL7HjzCZyizlLNBYdpauYX1Zy97v9VnZFQJDOAwP4/ai7ns N6eEDctoGTl5N77R9CmbuwLruvCLODuFlIhvi+C6ak+vxNFpbFMZpWGLK5CyAzyJA8fW pSpA2Bk9AMQI2fVZrDrRX6Pg5RYFb9bVuEvRN5cBFWKkw95OK527pFoQQALlkdqv/Sv4 Acm+6RUHeuWC8x/FLYmyH+C8Kv3ZmDGJkbeqKOJGgom7DOhYHT2WovGo3ROGeNiEW461 hEzQ== 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 :references:in-reply-to:date:cc:to:from:subject:message-id; bh=1yeg1j7St1XEdXHqjADPBA+WTr0Dg2qZYnX3F6QRAUk=; b=0uM2JmXRgzhGNp7jGR0qc/5u6D1+k+W162dD1TZkWn6pf/i60IL13dBVEEaxwPIFTO vd8AtZWjC/OkzuH916tn4m25mLhOxdzgc52QFTRmlDJpKOS2dqDvdcS6az9plArWY6eu 6w/O+qY7GDVfI7/YNjm9Gy5I8pHD0YTwZyp0rJzQ6UvBJyJkGrbwqYOojFIkIiQc9n8E QrcS2f2pFoFr/PEry4+Plf2EYCnbzQyNIvrrlLkNCE0fnEpsXTVpQXkZUTZI6mhv7TpY dgrwWnQEX8bISuWK4Xm8Ai5ws0KB3ALGkjMb1s8v9AOLnFgvv7sZPhsLgL9r7bEfdj4d EDFA== 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 d5si587958pls.190.2019.06.20.13.21.52; Thu, 20 Jun 2019 13:22:13 -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 S1726329AbfFTUVv (ORCPT + 99 others); Thu, 20 Jun 2019 16:21:51 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:45214 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725907AbfFTUVv (ORCPT ); Thu, 20 Jun 2019 16:21:51 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1he3Z7-0004xJ-P2; Thu, 20 Jun 2019 22:21:49 +0200 Message-ID: Subject: Re: [PATCH 3/3] nl80211: Include wiphy address setup in NEW_WIPHY From: Johannes Berg To: Denis Kenzior Cc: linux-wireless@vger.kernel.org Date: Thu, 20 Jun 2019 22:21:47 +0200 In-Reply-To: <144f36779085498bdc1b2f7ac0d0c267d431f51d.camel@sipsolutions.net> (sfid-20190620_220949_979394_9648D591) References: <20190619223606.4575-1-denkenz@gmail.com> <20190619223606.4575-3-denkenz@gmail.com> <7da9b924-78c7-ba72-fecc-a11700a34ff4@gmail.com> <44923833f1068e360b1f9534a9bbd37be41e4833.camel@sipsolutions.net> <427f488f-98f5-f888-f079-e2bbbb6eedf3@gmail.com> (sfid-20190620_220528_438291_AA97E7A5) <144f36779085498bdc1b2f7ac0d0c267d431f51d.camel@sipsolutions.net> (sfid-20190620_220949_979394_9648D591) 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 On Thu, 2019-06-20 at 22:09 +0200, Johannes Berg wrote: > > Sure, but you don't really need to know *everything* about the events > right there ... you can already filter which ones you care about > (perhaps you know you never want to bind hwsim ones for example) and > then request data on those that you do need. Btw, you can send a filter down when you do request the data, so you only get the data for the new wiphy you actually just discovered. So realistically, vs. your suggestion of sending all of the data in multiple events, that just adds 2 messages (the request and the data you already had), which isn't nearly as bad as you paint it. johannes