From: Andrew Lunn <andrew@lunn.ch>
To: David Laight <David.Laight@aculab.com>
Cc: Brian Masney <bmasney@redhat.com>,
"irusskikh@marvell.com" <irusskikh@marvell.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"cth451@gmail.com" <cth451@gmail.com>
Subject: Re: [PATCH] net: atlantic: fix check for invalid ethernet addresses
Date: Thu, 1 Dec 2022 03:22:25 +0100 [thread overview]
Message-ID: <Y4gP4W+CBSA7qD6a@lunn.ch> (raw)
In-Reply-To: <3adb7dc622a3429782ca89e83c8e020d@AcuMS.aculab.com>
> Pretty much zero chance of that board ever working well
> enough to be in a system.
IBM, for example, has at least three ranges. Maybe they could of
reached the end of one range, and simply continued shipping products
from the beginning of the next range...
aQuantia only has one range, so i would however agree for them, the
first valid MAC address is probably assigned to some internal
development device.
Andrew
next prev parent reply other threads:[~2022-12-01 2:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 17:42 [PATCH] net: atlantic: fix check for invalid ethernet addresses Brian Masney
2022-11-30 17:57 ` Brian Masney
2022-11-30 18:26 ` Tianhao Chai
2022-11-30 18:47 ` Brian Masney
2022-11-30 19:41 ` Andrew Lunn
2022-11-30 21:08 ` Brian Masney
2022-11-30 21:32 ` Andrew Lunn
2022-11-30 23:12 ` David Laight
2022-12-01 2:22 ` Andrew Lunn [this message]
2022-12-01 8:07 ` [EXT] " Igor Russkikh
2022-12-01 13:55 ` Brian Masney
2022-12-01 14:14 ` Andrew Lunn
2022-12-01 15:18 ` Igor Russkikh
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=Y4gP4W+CBSA7qD6a@lunn.ch \
--to=andrew@lunn.ch \
--cc=David.Laight@aculab.com \
--cc=bmasney@redhat.com \
--cc=cth451@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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