From: Flavio Suligoi <f.suligoi@asem.it>
To: David Miller <davem@davemloft.net>, "andrew@lunn.ch" <andrew@lunn.ch>
Cc: "jeffrey.t.kirsher@intel.com" <jeffrey.t.kirsher@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"andrew@lunn.ch" <andrew@lunn.ch>
Subject: RE: [PATCH v3] net: e1000e: add MAC address kernel cmd line parameter
Date: Fri, 1 Mar 2019 08:15:39 +0000 [thread overview]
Message-ID: <a9381ec45e9b4e5a8388c8414aadda98@asem.it> (raw)
In-Reply-To: <20190228.114707.11382969767373748.davem@davemloft.net>
> >> > Hi Flavio
> >> >
> >> > u-boot should be able to write the MAC address in the correct part of
> >> > device tree. Boards have been doing this a long time.
> >> >
> >> > Module parameters are considered bad. You should only do it if you
> >> > have no other option. Here you do have another options, so it is
> going
> >> > to be a hard sell getting David to access your patch.
> >> >
> >> > You will have more success by adding a call to
> >> > eth_platform_get_mac_address() to the e1000e driver.
> >>
> >> You have right, and thanks for your suggestions,
> >> but with a kernel parameter I can use the same method
> >> for any board where the NVM is missed, independently of any
> architecture
> >> (with or without the device tree presence - ARM or x86 or others).
> >
> > Hi Flavio
> >
> > Well, lets wait for David to say what he thinks about the module
> > parameter.
>
> I already rejected this, no way... Drivers that already have the
> unacceptable module parameter are no an argument for spreading this
> mistake further.
Hi David and Andrew,
ok, thank you for your suggestions and your time!
Flavio
next prev parent reply other threads:[~2019-03-01 8:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 9:20 [PATCH] " Flavio Suligoi
2019-02-28 13:38 ` [PATCH v2] " Flavio Suligoi
2019-02-28 13:52 ` [PATCH v3] " Flavio Suligoi
2019-02-28 15:32 ` Andrew Lunn
2019-02-28 15:51 ` Flavio Suligoi
2019-02-28 16:37 ` Andrew Lunn
2019-02-28 17:13 ` Flavio Suligoi
2019-02-28 19:29 ` Andrew Lunn
2019-02-28 19:47 ` David Miller
2019-03-01 8:15 ` Flavio Suligoi [this message]
2019-02-28 18:21 ` [PATCH] " David Miller
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=a9381ec45e9b4e5a8388c8414aadda98@asem.it \
--to=f.suligoi@asem.it \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®