From: Hongwei Zhang <hongweiz@ami.com>
To: <linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<openbmc@lists.ozlabs.org>, Jakub Kicinski <kuba@kernel.org>,
David S Miller <davem@davemloft.net>,
Heiner Kallweit <hkallweit1@gmail.com>
Cc: Hongwei Zhang <hongweiz@ami.com>, netdev <netdev@vger.kernel.org>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>
Subject: [Aspeed, v2 0/2] net: ftgmac100: Change the order of getting MAC address
Date: Tue, 22 Dec 2020 15:14:35 -0500 [thread overview]
Message-ID: <20201222201437.5588-1-hongweiz@ami.com> (raw)
In-Reply-To: <20201221205157.31501-2-hongweiz@ami.com>
Dear Reviewer,
Use native MAC address is preferred over other choices, thus change the order
of reading MAC address, try to read it from MAC chip first, if it's not
availabe, then try to read it from device tree.
Thanks,
--Hongwei
Changelog:
v2:
- Corrected comments in the patch
v1: https://patchwork.ozlabs.org/project/linux-aspeed/list/?series=221576
- Initial submission
Hongwei Zhang (1):
net: ftgmac100: Change the order of getting MAC address
drivers/net/ethernet/faraday/ftgmac100.c | 22 +++++++++++++---------
1 file changed, 13 insertions(+), 9 deletions(-)
--
2.17.1
next prev parent reply other threads:[~2020-12-22 20:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 20:51 [Aspeed, v1 0/1] net: ftgmac100: Change the order of getting MAC address Hongwei Zhang
2020-12-21 20:51 ` [Aspeed, v1 1/1] " Hongwei Zhang
2020-12-21 21:36 ` Heiner Kallweit
2020-12-22 20:14 ` Hongwei Zhang [this message]
2020-12-22 20:14 ` [Aspeed, v2 1/2] " Hongwei Zhang
2020-12-22 20:14 ` [Aspeed, v2 2/2] " Hongwei Zhang
2020-12-22 20:46 ` Heiner Kallweit
2020-12-22 21:00 ` Andrew Lunn
2020-12-28 22:01 ` Jakub Kicinski
2021-01-04 17:28 ` [Aspeed, v1 1/1] " Hongwei Zhang
2021-01-04 20:48 ` Heiner Kallweit
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=20201222201437.5588-1-hongweiz@ami.com \
--to=hongweiz@ami.com \
--cc=andrew@aj.id.au \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=joel@jms.id.au \
--cc=kuba@kernel.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).