Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4479052ybl; Tue, 20 Aug 2019 12:32:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqw47wzNrwYgbbownlacpXKJwKnE26OizHBS8Xilnh0Jj1FNdx9hr5wzbwPzjr8gMfaR0fEx X-Received: by 2002:a17:90a:fe5:: with SMTP id 92mr1568980pjz.35.1566329558000; Tue, 20 Aug 2019 12:32:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566329557; cv=none; d=google.com; s=arc-20160816; b=eA4qoXSSCvRIXT622Ph0OdwxAB1aPno/gA8waHbFzvvjz2xiNaZmsOWASFVImQwuSz oQGz7sZcSHGmg5QpAYm/s0NQYcE1BHPZ0wrnbtZXlZiH//FGpB+bOsiQj7m7oEzFsg7S xAQhDPcIyyv5lXJpQbIacPkUK0NK0zFv6gWz0VW1eVQ2eoVkD/1FDHf9y2SHXsGTkKVE yTiXtDJmJSNsoMFlAdA8bl4VK2KzU8zSWwUrrAUXTXNwH+hVz1772sY0cST0mtbSmtHN 6W6zjVt0eQzMg6fLCmqonCO5ql881NmD3MSDUZyRaSxR1tZV9aNR3IJoW7GQUPmMoPYz 51FQ== 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 :user-agent:references:in-reply-to:date:to:from:subject:message-id; bh=hiAG8LPMT2db0jttxyJhZaKYYNfaUcv8MciCaHhBUb0=; b=YW5LkzwORc+x3nk9NivUD8oBRBk3kw0yueuUHvDkQySWTszoncbwFBWDoKfZKZlk25 Ty98GhrjaJFZ0/+6MAlQVl/26/kxg5FYS2GMkEY42H/fRL7ZyIZLzRTHPnyuv/WmmQYN /9JP4B6nPNMtgeWIlCmKERl2Ghz1FPLMYNBrCu/RXjQGBZt1YEruAo+xpL91H697vsdw awi99YEcCsV6db8lqTIHTEtufSd1HIDlpzAODz15HM1+n0JFoyvnSEHoxShkQ4crsHky L3/aCOkFu8sV63uOkT3mx3TSv3YC0FSavV0K4frjG5OjAJibtMVSHGp/7CLBidmSuw/f YeFQ== 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 a4si12748239pls.185.2019.08.20.12.32.13; Tue, 20 Aug 2019 12:32:37 -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 S1730618AbfHTTcK (ORCPT + 99 others); Tue, 20 Aug 2019 15:32:10 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:42202 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729409AbfHTTcJ (ORCPT ); Tue, 20 Aug 2019 15:32:09 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1i09rT-0006fI-Ru; Tue, 20 Aug 2019 21:32:08 +0200 Message-ID: Subject: Re: [RFC 0/1] Allow MAC change on up interface From: Johannes Berg To: Denis Kenzior , James Prestwood , linux-wireless@vger.kernel.org Date: Tue, 20 Aug 2019 21:32:06 +0200 In-Reply-To: <7b9a7df3-6880-98f6-5c09-257165025559@gmail.com> (sfid-20190820_174845_396851_9BE0F3E7) References: <20190815185702.30937-1-prestwoj@gmail.com> <645af7dad899e8eb186b3fee0f8a8a151a408557.camel@sipsolutions.net> <394092a2f20697c9b055166a8254a5ef888551a5.camel@gmail.com> <4848c3a9d0b330fab4442436244387a2c127fa03.camel@sipsolutions.net> <1d975fec-a480-f40b-ff98-90d0e4852758@gmail.com> <72ac048c01619e0639fc182cd32818a5712cda1c.camel@sipsolutions.net> <7b9a7df3-6880-98f6-5c09-257165025559@gmail.com> (sfid-20190820_174845_396851_9BE0F3E7) Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) 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 Denis, Rather than replying to all the separate items here, just two things: 1) I'll reiterate - please keep things civil. You're taking things out of context a *lot* here, in what seems like an attempt to draw a parallel between my and your utterances. 2) I'll take your point that I've been somewhat dismissive in tone, and will try to change that. I do want to reply to two things specifically though: > Fine. I get that. But how about asking what the use case is? Or say > you don't quite understand why something is needed? Really, I should *not* have to ask that. You should consider it your obligation to provide enough information for me to review patches without having to go back and ask what it is you actually want to achieve. Compared to some other subsystems and maintainers I've dealt with, I think I've actually been rather patient in trying to extract the purpose of your changes, rather than *really* just dismissing them (which I've felt like many times.) > a maintainer who's job (by definition) > is to encourage new contributors and improve the subsystem he > maintains...? This is what maybe you see as the maintainer's role, but I disagree, at least to some extent. I see the role more of a supervisor, somebody who's ensuring that all the changes coming in will work together. Yes, I have my own incentive to improve things, but if you have a particular incentive to improve a particular use case, the onus really is on you to convince me of that, not on me to try to ferret the reasoning out of you and make those improvements my own. So please - come with some actual reasoning. This particular thread only offered "would elminate a few potential race conditions", in the cover letter, not even the patch itself, so it wasn't very useful. I was perhaps less than courteous trying to extract the reasoning, but I shouldn't have to in the first place. Thanks, johannes