From: Oliver Neukum <oneukum@suse.com>
To: "Bjørn Mork" <bjorn@mork.no>, "Oliver Neukum" <oneukum@suse.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] usbnet: assign unique random MAC
Date: Thu, 16 Nov 2023 14:29:43 +0100 [thread overview]
Message-ID: <6eba35aa-c20e-434d-9d4d-71c1c06c7a1d@suse.com> (raw)
In-Reply-To: <87il61g7fz.fsf@miraculix.mork.no>
On 16.11.23 14:21, Bjørn Mork wrote:
> Oliver Neukum <oneukum@suse.com> writes:
>
>> On 16.11.23 13:39, Bjørn Mork wrote:
>>> Oliver Neukum <oneukum@suse.com> writes:
>> Isn't it a bit evil to change behavior?
>
> Only if someone actually depend on the old behaviour. And I think
> there's a fair chance no one does.
Very well. I'll take it out.
>> Do you think I should make a different version for stable
>> with the logic for retaining the old behavior inverted?
>
> I assumed this was unsuitable for stable backports. Is there any reason
> to backport it?
You could argue that handing out the same MAC twice
violates standards.
Regards
Oliver
next prev parent reply other threads:[~2023-11-16 13:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 12:30 [RFC] usbnet: assign unique random MAC Oliver Neukum
2023-11-16 12:39 ` Bjørn Mork
2023-11-16 13:02 ` Oliver Neukum
2023-11-16 13:21 ` Bjørn Mork
2023-11-16 13:29 ` Oliver Neukum [this message]
2023-11-16 14:49 ` Bjørn Mork
2023-11-16 17:45 ` Oliver Neukum
2023-11-16 21:47 ` Andrew Lunn
2023-11-16 18:49 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2023-11-16 14:05 Oliver Neukum
2023-11-16 18:51 ` Stephen Hemminger
2023-11-16 20:48 ` Benjamin Poirier
2023-11-20 10:44 ` Oliver Neukum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6eba35aa-c20e-434d-9d4d-71c1c06c7a1d@suse.com \
--to=oneukum@suse.com \
--cc=bjorn@mork.no \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).