Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4505331ybl; Tue, 20 Aug 2019 13:03:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqwugpQrhOruywMvXbLvO6X+XV/54m1RT7K4iIqU7lpkwwOgcB5+WjELaVIzroifND0JhMd9 X-Received: by 2002:a17:90a:22f0:: with SMTP id s103mr1755282pjc.56.1566331398640; Tue, 20 Aug 2019 13:03:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566331398; cv=none; d=google.com; s=arc-20160816; b=PNCp0ltgTZk/0CY/OIwrKi5ypP5fdp7IAIrM3sJXhpYgdvz7XzgNcdBC9DbGm2H1SA HTVQEAkPUhVIWynF8A+tc7EBfV2TYBWbFZTx+TKH2QtK35Dj+NOche6MoDSMJb0f60wH Bh+W445ugV04g/TtuO6xNMMDKQ5mEoL/xaGuH1wrzz7FmoQ8Lw8fr7U1tubnxcAPCx8g JKbYBliuIrFfX/cUmw70t4Y30eVIoEBpBHowVz3bLdlghbFvogx35B0xB7xVSzff4OGr 4FAfDmSWPuGeP6TdhDmuhOTlNOwG6LmSVXWeIA1q8hwRm6PolXyKgETBLjE3qptJ+Zkr IcWQ== 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=P9bF+ALX1YT5TWnkrMTAyq8lP7rzjL2wbyzOoJc6PyA=; b=byUhhBVZPnT9iTpINtNwZm6z/jGQOGf7QXQjh+YjfU/Ja/qrSA9sJlLnv9G8K/ykwX 0q2NdTYu97swCGb/19cylL37imsbi8P6S90oLfDKER09Mbn/73R5QlmTufteYVhjI95x lHtn8/Ub6HMEZSnv5MmeqKY9/1tRXg3TGkfX4bMhZb3UrjyHa7adGFgnK3/SSKaGUqXi AIj7n20VcBhFqE9fjyOfrwHTeauU/a19Paf6fPzyo0MkbGLKMT+jqPJ7acOc0cKz8TIO lFF2h3J4iSwH+Pf498iQTxdsgNrM8AV/fCLEZqKmn2pGsuxNjQFdZhzasY3OKn41CViN xn1w== 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 p4si7725475pli.307.2019.08.20.13.02.59; Tue, 20 Aug 2019 13:03:18 -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 S1730809AbfHTUB0 (ORCPT + 99 others); Tue, 20 Aug 2019 16:01:26 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:42750 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729950AbfHTUB0 (ORCPT ); Tue, 20 Aug 2019 16:01:26 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1i0AJo-0007If-D2; Tue, 20 Aug 2019 22:01:24 +0200 Message-ID: <3dc266154b11381c8f019712e2203b5cbfd3a6da.camel@sipsolutions.net> 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 22:01:23 +0200 In-Reply-To: (sfid-20190820_215433_125295_49BCBF06) 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_215433_125295_49BCBF06) 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, > So let me ask you this. What do you _want_ to see when a contributor > submits something as an RFC, which that contributor states is not ready > for 'true' review and is really there to generate feedback? > > Do you want to have that contributor use a different prefix? Every > maintainer is differrent. I get that. So if we want to start an actual > brainstorming session with you, how do we accomplish that? I'd be happy if you were to just state what you want to achieve, for starters! Whether it's [RFC] with a cover letter saying "hey, we feel this could be faster, and have come up with the following as an idea", or just another email without any code changes saying "hey, we feel this could be faster, how do you think we could do this" ... doesn't really matter. What you have *actually* been doing though (at least from my perspective) is something along the lines of "hey, here's a new way to do " without even really stating why the existing doesn't work for you. And where I questioned the need to have a new way to do , well, we got the other part of this thread. > So this goes back to my earlier point. How do you want us to start a > discussion with you such that you don't become a 'supervisor' and > instead try to understand the pain points first? Just explaining the pain points would help? johannes