From: kbuild test robot <lkp@intel.com>
To: Raghuram Chary J <raghuramchary.jallipalli@microchip.com>
Cc: kbuild-all@01.org, davem@davemloft.net, netdev@vger.kernel.org,
unglinuxdriver@microchip.com, woojung.huh@microchip.com,
raghuramchary.jallipalli@microchip.com
Subject: [RFC PATCH] lan78xx: lan78xx_regs[] can be static
Date: Thu, 12 Apr 2018 02:51:47 +0800 [thread overview]
Message-ID: <20180411185147.GA48599@lkp-ivb-ep02> (raw)
In-Reply-To: <20180411072450.9809-3-raghuramchary.jallipalli@microchip.com>
Fixes: 1373bfc60bd8 ("lan78xx: Add support to dump lan78xx registers")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
lan78xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/usb/lan78xx.c b/drivers/net/usb/lan78xx.c
index cbeec78..df5c3eb 100644
--- a/drivers/net/usb/lan78xx.c
+++ b/drivers/net/usb/lan78xx.c
@@ -278,7 +278,7 @@ struct lan78xx_statstage64 {
u64 eee_tx_lpi_time;
};
-u32 lan78xx_regs[] = {
+static u32 lan78xx_regs[] = {
ID_REV,
INT_STS,
HW_CFG,
next prev parent reply other threads:[~2018-04-11 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 7:24 [PATCH v1 net 0/3] lan78xx: Fixes and enhancements Raghuram Chary J
2018-04-11 7:24 ` [PATCH v1 net 1/3] lan78xx: PHY DSP registers initialization to address EEE link drop issues with long cables Raghuram Chary J
2018-04-11 7:24 ` [PATCH v1 net 2/3] lan78xx: Add support to dump lan78xx registers Raghuram Chary J
2018-04-11 18:51 ` kbuild test robot
2018-04-11 18:51 ` kbuild test robot [this message]
2018-04-11 7:24 ` [PATCH v1 net 3/3] lan78xx: Lan7801 Support for Fixed PHY Raghuram Chary J
2018-04-11 12:55 ` [PATCH v1 net 0/3] lan78xx: Fixes and enhancements Andrew Lunn
2018-04-11 14:20 ` David Miller
2018-04-11 14:54 ` RaghuramChary.Jallipalli
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=20180411185147.GA48599@lkp-ivb-ep02 \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=raghuramchary.jallipalli@microchip.com \
--cc=unglinuxdriver@microchip.com \
--cc=woojung.huh@microchip.com \
/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