From: Oliver Neukum <oneukum@suse.com>
To: Andrew Lunn <andrew@lunn.ch>, Oliver Neukum <oneukum@suse.com>
Cc: hayeswang@realtek.com, netdev@vger.kernel.org
Subject: Re: [RFC] r8152: pass through needs to be singular
Date: Thu, 4 Aug 2022 15:29:40 +0200 [thread overview]
Message-ID: <3017563c-0085-ae88-1ef0-40d1f89ef4c5@suse.com> (raw)
In-Reply-To: <YuvIqCBAcZTMh0xV@lunn.ch>
On 04.08.22 15:24, Andrew Lunn wrote:
> The problem is regressions. Current code will put the MAC address on
> both. I guess most users just have one dock with a cabled and the
> second is unused. Both will get the same MAC address, the DHCP server
> will recognise the MAC address and give out the expected IP address.
1. That is a rather esoteric situation in which a bug is exploited
2. We are at a philosophical point where I need to argue that fixing
a bug is necessarily a change in behavior.
> I would expect whatever MAC address is in the netdev structure to be
> put on the interface at resume. That should of been the MAC it was
> using before suspend. And by doing that, you bypass all the discussion
> about where it came from.
Debatable, but that's not what the driver does. It reacquires the MAC
from the firmware. I want to change that. Though obviously that changes
behavior.
I am sorry, but at some point a bug is a bug, even if some people like
it.
Regards
Oliver
next prev parent reply other threads:[~2022-08-04 13:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 19:18 [RFC] r8152: pass through needs to be singular Oliver Neukum
2022-07-28 22:11 ` Andrew Lunn
2022-08-02 10:52 ` Oliver Neukum
2022-08-02 13:31 ` Andrew Lunn
2022-08-04 9:24 ` Oliver Neukum
2022-08-04 13:24 ` Andrew Lunn
2022-08-04 13:29 ` Oliver Neukum [this message]
2022-08-04 14:31 ` Andrew Lunn
2022-08-03 3:48 ` Hayes Wang
2022-08-04 8:57 ` Oliver Neukum
2022-08-08 7:04 ` Hayes Wang
2022-08-23 7:53 ` 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=3017563c-0085-ae88-1ef0-40d1f89ef4c5@suse.com \
--to=oneukum@suse.com \
--cc=andrew@lunn.ch \
--cc=hayeswang@realtek.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.