From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH] netdev/phy: Make get_phy_id() static and quit EXPORTing it.
Date: Tue, 15 May 2012 17:32:08 -0400 [thread overview]
Message-ID: <20120515213208.GD17760@windriver.com> (raw)
In-Reply-To: <1337114812-3912-1-git-send-email-ddaney.cavm@gmail.com>
[[PATCH] netdev/phy: Make get_phy_id() static and quit EXPORTing it.] On 15/05/2012 (Tue 13:46) David Daney wrote:
> From: David Daney <david.daney@cavium.com>
>
> This function is only referenced from within phy_device.c, so there is
> no reason to export it. In fact, we can make it static.
I did a bit of data mining to remind myself why it was exported. Back
in a01b3d766c (v2.6.26) gianfar_mii was using it. That then got merged
into fsl_pq_mdio.c and gianfar_mii was deleted. Then finally in commit
28d8ea2d568 (v3.2) the one instance of code that was using it got
removed. So, I think this should be OK (but for net-next, though).
Acked-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Paul.
--
>
> Signed-off-by: David Daney <david.daney@cavium.com>
> ---
> drivers/net/phy/phy_device.c | 3 +--
> include/linux/phy.h | 1 -
> 2 files changed, 1 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/phy/phy_device.c b/drivers/net/phy/phy_device.c
> index e8c42d6..de86a55 100644
> --- a/drivers/net/phy/phy_device.c
> +++ b/drivers/net/phy/phy_device.c
> @@ -207,7 +207,7 @@ static struct phy_device* phy_device_create(struct mii_bus *bus,
> * Description: Reads the ID registers of the PHY at @addr on the
> * @bus, stores it in @phy_id and returns zero on success.
> */
> -int get_phy_id(struct mii_bus *bus, int addr, u32 *phy_id)
> +static int get_phy_id(struct mii_bus *bus, int addr, u32 *phy_id)
> {
> int phy_reg;
>
> @@ -230,7 +230,6 @@ int get_phy_id(struct mii_bus *bus, int addr, u32 *phy_id)
>
> return 0;
> }
> -EXPORT_SYMBOL(get_phy_id);
>
> /**
> * get_phy_device - reads the specified PHY device and returns its @phy_device struct
> diff --git a/include/linux/phy.h b/include/linux/phy.h
> index 6fe0a37..9039009 100644
> --- a/include/linux/phy.h
> +++ b/include/linux/phy.h
> @@ -477,7 +477,6 @@ static inline int phy_write(struct phy_device *phydev, u32 regnum, u16 val)
> return mdiobus_write(phydev->bus, phydev->addr, regnum, val);
> }
>
> -int get_phy_id(struct mii_bus *bus, int addr, u32 *phy_id);
> struct phy_device* get_phy_device(struct mii_bus *bus, int addr);
> int phy_device_register(struct phy_device *phy);
> int phy_init_hw(struct phy_device *phydev);
> --
> 1.7.2.3
>
next prev parent reply other threads:[~2012-05-15 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 20:46 [PATCH] netdev/phy: Make get_phy_id() static and quit EXPORTing it David Daney
2012-05-15 21:32 ` Paul Gortmaker [this message]
2012-05-16 4:59 ` 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=20120515213208.GD17760@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).