From: Andrew Lunn <andrew@lunn•ch>
To: Andy Duan <fugang.duan@nxp•com>
Cc: "davem@davemloft•net" <davem@davemloft•net>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"ynezz@true•cz" <ynezz@true•cz>,
"john@phrozen•org" <john@phrozen•org>,
"bgolaszewski@baylibre•com" <bgolaszewski@baylibre•com>
Subject: Re: [PATCH net 2/3] of_net: add property "nvmem-mac-address" for of_get_mac_addr()
Date: Fri, 10 May 2019 20:17:58 +0200 [thread overview]
Message-ID: <20190510181758.GF11588@lunn.ch> (raw)
In-Reply-To: <1557476567-17397-3-git-send-email-fugang.duan@nxp.com>
On Fri, May 10, 2019 at 08:24:03AM +0000, Andy Duan wrote:
> If MAC address read from nvmem cell and it is valid mac address,
> .of_get_mac_addr_nvmem() add new property "nvmem-mac-address" in
> ethernet node. Once user call .of_get_mac_address() to get MAC
> address again, it can read valid MAC address from device tree in
> directly.
I suspect putting the MAC address into OF will go away in a follow up
patch. It is a bad idea.
Andrew
next prev parent reply other threads:[~2019-05-10 18:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 8:23 [PATCH net 0/3] add property "nvmem_macaddr_swap" to swap macaddr bytes order Andy Duan
2019-05-10 8:24 ` [PATCH net 1/3] net: ethernet: " Andy Duan
2019-05-10 18:16 ` Andrew Lunn
2019-05-13 3:10 ` [EXT] " Andy Duan
2019-05-10 8:24 ` [PATCH net 2/3] of_net: add property "nvmem-mac-address" for of_get_mac_addr() Andy Duan
2019-05-10 18:17 ` Andrew Lunn [this message]
2019-05-13 3:31 ` [EXT] " Andy Duan
2019-05-13 8:00 ` Petr Štetiar
2019-05-13 8:47 ` Andy Duan
2019-05-10 8:24 ` [PATCH net 3/3] dt-bindings: doc: add new properties for of_get_mac_address from nvmem Andy Duan
2019-05-10 11:28 ` [PATCH net 0/3] add property "nvmem_macaddr_swap" to swap macaddr bytes order Petr Štetiar
2019-05-10 11:31 ` Maxime Ripard
2019-05-11 14:44 ` NVMEM address DT post processing [Was: Re: [PATCH net 0/3] add property "nvmem_macaddr_swap" to swap macaddr bytes order] Petr Štetiar
2019-05-12 12:19 ` Maxime Ripard
2019-05-13 9:28 ` Petr Štetiar
2019-05-13 8:25 ` Srinivas Kandagatla
2019-05-13 9:07 ` Petr Štetiar
2019-05-13 10:06 ` Srinivas Kandagatla
2019-05-13 11:16 ` Petr Štetiar
2019-05-14 15:13 ` Srinivas Kandagatla
2019-05-14 17:44 ` Petr Štetiar
2019-05-15 17:12 ` Srinivas Kandagatla
2019-05-20 14:28 ` Rob Herring
2019-05-13 3:38 ` [EXT] Re: [PATCH net 0/3] add property "nvmem_macaddr_swap" to swap macaddr bytes order Andy Duan
2019-05-13 9:35 ` ynezz
2019-05-13 3:06 ` [EXT] " Andy Duan
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=20190510181758.GF11588@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=bgolaszewski@baylibre$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=fugang.duan@nxp$(echo .)com \
--cc=john@phrozen$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=ynezz@true$(echo .)cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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