From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH net-next 09/14] net: emaclite: remove empty MDIO bus reset function
Date: Wed, 26 Mar 2014 18:07:21 -0700 [thread overview]
Message-ID: <1395882446-552-10-git-send-email-f.fainelli@gmail.com> (raw)
In-Reply-To: <1395882446-552-1-git-send-email-f.fainelli@gmail.com>
xemaclite_mdio_reset() does nothing useful and is optional for the MDIO
bus code, so let's just remove it.
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
---
drivers/net/ethernet/xilinx/xilinx_emaclite.c | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/drivers/net/ethernet/xilinx/xilinx_emaclite.c b/drivers/net/ethernet/xilinx/xilinx_emaclite.c
index 58756617644f..0d87c67a5ff7 100644
--- a/drivers/net/ethernet/xilinx/xilinx_emaclite.c
+++ b/drivers/net/ethernet/xilinx/xilinx_emaclite.c
@@ -795,18 +795,6 @@ static int xemaclite_mdio_write(struct mii_bus *bus, int phy_id, int reg,
}
/**
- * xemaclite_mdio_reset - Reset the mdio bus.
- * @bus: Pointer to the MII bus
- *
- * This function is required(?) as per Documentation/networking/phy.txt.
- * There is no reset in this device; this function always returns 0.
- */
-static int xemaclite_mdio_reset(struct mii_bus *bus)
-{
- return 0;
-}
-
-/**
* xemaclite_mdio_setup - Register mii_bus for the Emaclite device
* @lp: Pointer to the Emaclite device private data
* @ofdev: Pointer to OF device structure
@@ -861,7 +849,6 @@ static int xemaclite_mdio_setup(struct net_local *lp, struct device *dev)
bus->name = "Xilinx Emaclite MDIO";
bus->read = xemaclite_mdio_read;
bus->write = xemaclite_mdio_write;
- bus->reset = xemaclite_mdio_reset;
bus->parent = dev;
bus->irq = lp->mdio_irqs; /* preallocated IRQ table */
--
1.8.3.2
next prev parent reply other threads:[~2014-03-27 1:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 1:07 [PATCH net-next 00/14] net: remove empty MDIO bus reset functions Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 01/14] net: greth: remove empty MDIO bus reset function Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 02/14] tg3: " Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 03/14] macb: " Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 04/14] dnet: " Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 05/14] net: ethoc: remove empty MDIO bus function Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 06/14] fec: " Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 07/14] fs_enet: " Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 08/14] net: mvmdio: remove empty MDIO bus reset function Florian Fainelli
2014-03-27 1:07 ` Florian Fainelli [this message]
2014-03-27 1:07 ` [PATCH net-next 10/14] net: sun4i: " Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 11/14] net: ftgmac100: " Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 12/14] r6040: " Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 13/14] bfin_mac: " Florian Fainelli
2014-03-27 1:07 ` [PATCH net-next 14/14] Documentation: networking: phy.txt: MDIO bus reset is optional Florian Fainelli
2014-03-27 4:19 ` [PATCH net-next 00/14] net: remove empty MDIO bus reset functions David Miller
2014-03-27 17:17 ` Florian Fainelli
2014-03-27 18:40 ` 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=1395882446-552-10-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--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).