From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: Ramon Fried <rfried.dev@gmail.com>,
Michael Walle <michael@walle.cc>,
Michal Simek <michal.simek@xilinx.com>,
Grygorii Strashko <grygorii.strashko@ti.com>,
git <git@xilinx.com>, Joe Hershberger <joe.hershberger@ni.com>,
Simon Glass <sjg@chromium.org>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH] net: uclass: Save ethernet MAC address when generated
Date: Thu, 18 Nov 2021 10:46:28 +0100 [thread overview]
Message-ID: <1901784.1637228788@gemini.denx.de> (raw)
In-Reply-To: <1889944.1637219294@gemini.denx.de>
Dear Tom,
In message <1889944.1637219294@gemini.denx.de> I wrote:
>
> > We're about to
> > introduce the 3rd variant. I'd feel a whole lot better about taking in
> > a v2 of this patch that correct the help (and maybe updates
> > doc/README.enetaddr!) if someone could report back on what's going on
> > with the layerscape, imx* and socfpga platforms. There's in fact a
> > number of platforms enabling it that I'm pretty sure DENX has or had the
> > hardware on, so can we get some spot checking done there?
>
> I will check and provide an update later, but from the best of my
> knowledge none of the boards we ported actually need or use this
> feature. This is just a copy&paste mess.
We could not find even a single board maintained or upstreamed
by DENX where NET_RANDOM_ETHADDR was even mentioned in the
specifications, and certainly not a mandatory feature.
That's all copy & paste garbage.
Viele Grüße,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
The human mind treats a new idea the way the body treats a strange
protein - it rejects it. - P. Medawar
next prev parent reply other threads:[~2021-11-18 9:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 11:14 [PATCH] net: uclass: Save ethernet MAC address when generated Michal Simek
2021-11-01 20:25 ` Ramon Fried
2021-11-02 9:00 ` Michael Walle
2021-11-02 10:27 ` Michal Simek
2021-11-03 16:57 ` Tom Rini
2021-11-04 11:18 ` Michal Simek
2021-11-04 11:37 ` Tom Rini
2021-11-04 11:43 ` Michal Simek
2021-11-04 12:59 ` Tom Rini
2021-11-04 13:06 ` Michal Simek
2021-11-04 2:09 ` Grygorii Strashko
2021-11-04 11:16 ` Michal Simek
2021-11-04 12:27 ` Michael Walle
2021-11-04 13:15 ` Michal Simek
2021-11-04 13:40 ` Michael Walle
2021-11-04 21:00 ` Ramon Fried
2021-11-09 13:55 ` Michael Walle
2021-11-11 9:10 ` Michael Walle
2021-11-16 14:18 ` Tom Rini
2021-11-16 14:56 ` Wolfgang Denk
2021-11-16 18:41 ` Tom Rini
2021-11-17 7:44 ` Wolfgang Denk
2021-11-17 11:50 ` Tom Rini
2021-11-17 12:24 ` Wolfgang Denk
2021-11-17 12:35 ` Tom Rini
2021-11-17 15:56 ` Wolfgang Denk
2021-11-17 16:15 ` Tom Rini
2021-11-18 7:08 ` Wolfgang Denk
2021-11-18 9:46 ` Wolfgang Denk [this message]
2021-11-18 14:51 ` Tom Rini
2021-11-18 16:29 ` Tom Rini
2021-11-18 19:04 ` Wolfgang Denk
2021-11-18 19:54 ` Tom Rini
2021-11-19 12:30 ` Michal Simek
2021-11-20 15:56 ` Tom Rini
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=1901784.1637228788@gemini.denx.de \
--to=wd@denx.de \
--cc=git@xilinx.com \
--cc=grygorii.strashko@ti.com \
--cc=joe.hershberger@ni.com \
--cc=michael@walle.cc \
--cc=michal.simek@xilinx.com \
--cc=rfried.dev@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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).