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;
Subject: Re: [RFC 0/1] Allow MAC change on up interface
To:     Dan Williams <dcbw@redhat.com>,
        Johannes Berg <johannes@sipsolutions.net>,
        James Prestwood <prestwoj@gmail.com>,
        linux-wireless@vger.kernel.org
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>
 <32547793981b3997f7e0f74137745f38615e5c54.camel@redhat.com>
From:   Denis Kenzior <denkenz@gmail.com>
Message-ID: <32a1bddd-2472-10a3-4d0d-5634814e635b@gmail.com>
Date:   Tue, 20 Aug 2019 13:21:04 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <32547793981b3997f7e0f74137745f38615e5c54.camel@redhat.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

Hi Dan,

On 8/20/19 12:53 PM, Dan Williams wrote:
> On Tue, 2019-08-20 at 10:40 -0500, Denis Kenzior wrote:
>> Hi Johannes,
>>
>>> Stop.
>>>
>>> Your tone, and in particular the constant snide comments and
>>> attacks on
>>> me are, quite frankly, getting extremely tiring.
>>>
>>
>> Look, I'm sorry I hit a nerve, but from where I am sitting, it had to
>> be
>> said...
> 
> But did it really? And in that way?  There were certainly better ways
> to go about that response.

The issue is that this isn't the first such occurrence.  There is a 
pattern here and it needs to change.  So +1 on handling this better.

> 
> I don't recall seeing a NAK anywhere his email chain (which you'd get
> with some other kernel maintainers) but instead (a) an explanation of
> why the proposed solution had some problems, (b) some alternative
> possibilities and (c) requests for more information so the discussion
> could continue.

So the cover letter states:
"Set IFF_LIVE_ADDR_CHANGE on net_device. Note: I know setting this
    where I did is likely not the right way to do it, but for this
    proof-of-concept it works. With guidance I can move this around
    to a proper place."

and I'll leave it up to you to read the first response from the maintainer.

> 
> It does the requested changes no good to take that kind of tone. Let's

Neither is:
"don't do that then"

or

"I'm not really sure I see any point in this to start with"

or

"To me, the whole thing seems like more of a problem than a solution."

> move on from here and keep things constructive to solve the problem at
> hand, which is:
> 
> "Changing the MAC address of a WiFi interface takes longer than I'd
> like and clears some state that I'd like it to keep."
> 
> That is a technical problem we can solve, so let's keep it at that
> level.
> 

I'm all for moving on and having the people that know this stuff well 
giving actual guidance, as was requested originally.

Regards,
-Denis