From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next 12/15] lasi_82594: use eth_hw_addr_set()
Date: Thu, 18 Nov 2021 23:10:30 -0800 [thread overview]
Message-ID: <20211119071033.3756560-13-kuba@kernel.org> (raw)
In-Reply-To: <20211119071033.3756560-1-kuba@kernel.org>
dev_addr is set from IO reads, passed to an arch-specific helper.
Note that the helper never reads it so uninitialized temp is fine.
Fixes build on parisc.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
drivers/net/ethernet/i825xx/lasi_82596.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/i825xx/lasi_82596.c b/drivers/net/ethernet/i825xx/lasi_82596.c
index 48e001881c75..0af70094aba3 100644
--- a/drivers/net/ethernet/i825xx/lasi_82596.c
+++ b/drivers/net/ethernet/i825xx/lasi_82596.c
@@ -147,6 +147,7 @@ lan_init_chip(struct parisc_device *dev)
struct net_device *netdevice;
struct i596_private *lp;
int retval = -ENOMEM;
+ u8 addr[ETH_ALEN];
int i;
if (!dev->irq) {
@@ -167,13 +168,14 @@ lan_init_chip(struct parisc_device *dev)
netdevice->base_addr = dev->hpa.start;
netdevice->irq = dev->irq;
- if (pdc_lan_station_id(netdevice->dev_addr, netdevice->base_addr)) {
+ if (pdc_lan_station_id(addr, netdevice->base_addr)) {
for (i = 0; i < 6; i++) {
- netdevice->dev_addr[i] = gsc_readb(LAN_PROM_ADDR + i);
+ addr[i] = gsc_readb(LAN_PROM_ADDR + i);
}
printk(KERN_INFO
"%s: MAC of HP700 LAN read from EEPROM\n", __FILE__);
}
+ eth_hw_addr_set(netdevice, addr);
lp = netdev_priv(netdevice);
lp->options = dev->id.sversion == 0x72 ? OPT_SWAP_PORT : 0;
--
2.31.1
next prev parent reply other threads:[~2021-11-19 7:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 7:10 [PATCH net-next 00/15] use eth_hw_addr_set() in arch-specific drivers Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 01/15] amd: lance: use eth_hw_addr_set() Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 02/15] amd: ni65: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 03/15] amd: a2065/ariadne: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 04/15] amd: hplance: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 05/15] amd: atarilance: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 06/15] amd: mvme147: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 07/15] 8390: smc-ultra: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 08/15] 8390: hydra: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 09/15] 8390: mac8390: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 10/15] 8390: wd: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 11/15] smc9194: " Jakub Kicinski
2021-11-19 7:10 ` Jakub Kicinski [this message]
2021-11-19 7:10 ` [PATCH net-next 13/15] apple: macmace: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 14/15] cirrus: mac89x0: " Jakub Kicinski
2021-11-19 7:10 ` [PATCH net-next 15/15] natsemi: macsonic: " Jakub Kicinski
2021-11-19 11:20 ` [PATCH net-next 00/15] use eth_hw_addr_set() in arch-specific drivers patchwork-bot+netdevbpf
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=20211119071033.3756560-13-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).