From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next 3/4] net: phy: stop exporting phy_queue_state_machine
Date: Thu, 13 Feb 2025 22:50:02 +0100 [thread overview]
Message-ID: <16986d3d-7baf-4b02-a641-e2916d491264@gmail.com> (raw)
In-Reply-To: <d14f8a69-dc21-4ff7-8401-574ffe2f4bc5@gmail.com>
phy_queue_state_machine() isn't used outside phy.c,
so stop exporting it.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
drivers/net/phy/phy.c | 4 ++--
include/linux/phy.h | 1 -
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/net/phy/phy.c b/drivers/net/phy/phy.c
index d0c1718e2..8738ffb4c 100644
--- a/drivers/net/phy/phy.c
+++ b/drivers/net/phy/phy.c
@@ -520,12 +520,12 @@ int __phy_hwtstamp_set(struct phy_device *phydev,
* @phydev: the phy_device struct
* @jiffies: Run the state machine after these jiffies
*/
-void phy_queue_state_machine(struct phy_device *phydev, unsigned long jiffies)
+static void phy_queue_state_machine(struct phy_device *phydev,
+ unsigned long jiffies)
{
mod_delayed_work(system_power_efficient_wq, &phydev->state_queue,
jiffies);
}
-EXPORT_SYMBOL(phy_queue_state_machine);
/**
* phy_trigger_machine - Trigger the state machine to run now
diff --git a/include/linux/phy.h b/include/linux/phy.h
index 33e2c2c93..bb7454364 100644
--- a/include/linux/phy.h
+++ b/include/linux/phy.h
@@ -2061,7 +2061,6 @@ int phy_drivers_register(struct phy_driver *new_driver, int n,
struct module *owner);
void phy_error(struct phy_device *phydev);
void phy_state_machine(struct work_struct *work);
-void phy_queue_state_machine(struct phy_device *phydev, unsigned long jiffies);
void phy_trigger_machine(struct phy_device *phydev);
void phy_mac_interrupt(struct phy_device *phydev);
void phy_start_machine(struct phy_device *phydev);
--
2.48.1
next prev parent reply other threads:[~2025-02-13 21:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 21:47 [PATCH net-next 0/4] net: phy: clean up phy.h Heiner Kallweit
2025-02-13 21:48 ` [PATCH net-next 1/4] net: phy: remove fixup-related definitions from phy.h which are not used outside phylib Heiner Kallweit
2025-02-14 10:59 ` Mateusz Polchlopek
2025-02-14 11:11 ` Heiner Kallweit
2025-02-14 15:49 ` Andrew Lunn
2025-02-14 14:51 ` Russell King (Oracle)
2025-02-13 21:49 ` [PATCH net-next 2/4] net: phy: stop exporting feature arrays which aren't " Heiner Kallweit
2025-02-14 11:10 ` Mateusz Polchlopek
2025-02-14 14:52 ` Russell King (Oracle)
2025-02-13 21:50 ` Heiner Kallweit [this message]
2025-02-14 11:00 ` [PATCH net-next 3/4] net: phy: stop exporting phy_queue_state_machine Mateusz Polchlopek
2025-02-14 14:53 ` Russell King (Oracle)
2025-02-13 21:51 ` [PATCH net-next 4/4] net: phy: remove helper phy_is_internal Heiner Kallweit
2025-02-14 11:01 ` Mateusz Polchlopek
2025-02-14 14:54 ` Russell King (Oracle)
2025-02-15 1:20 ` [PATCH net-next 0/4] net: phy: clean up phy.h 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=16986d3d-7baf-4b02-a641-e2916d491264@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).