From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Greg Ungerer" <gerg@linux-m68k.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Vladimir Oltean" <olteanv@gmail.com>,
"Doug Berger" <opendmb@gmail.com>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Thangaraj Samynathan" <Thangaraj.S@microchip.com>,
"Rengarajan Sundararajan" <Rengarajan.S@microchip.com>,
"Microchip Linux Driver Support" <UNGLinuxDriver@microchip.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"Russell King - ARM Linux" <linux@armlinux.org.uk>,
"David Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Eric Dumazet" <edumazet@google.com>
Cc: Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org,
Linux USB Mailing List <linux-usb@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/3] net: phy: fixed_phy: simplifications and improvements
Date: Sat, 17 May 2025 22:33:23 +0200 [thread overview]
Message-ID: <4d4c468e-300d-42c7-92a1-eabbdb6be748@gmail.com> (raw)
This series includes two types of changes:
- All callers pass PHY_POLL, therefore remove irq argument
- constify the passed struct fixed_phy_status *status
Heiner Kallweit (3):
net: phy: fixed_phy: remove irq argument from fixed_phy_add
net: phy: fixed_phy: remove irq argument from fixed_phy_register
net: phy: fixed_phy: constify status argument where possible
arch/m68k/coldfire/m5272.c | 2 +-
arch/mips/bcm47xx/setup.c | 2 +-
drivers/net/dsa/dsa_loop.c | 2 +-
drivers/net/ethernet/broadcom/bgmac.c | 2 +-
drivers/net/ethernet/broadcom/genet/bcmmii.c | 2 +-
drivers/net/ethernet/faraday/ftgmac100.c | 2 +-
drivers/net/mdio/of_mdio.c | 2 +-
drivers/net/phy/fixed_phy.c | 12 +++++-------
drivers/net/usb/lan78xx.c | 2 +-
include/linux/phy_fixed.h | 18 ++++++++----------
10 files changed, 21 insertions(+), 25 deletions(-)
--
2.49.0
next reply other threads:[~2025-05-17 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 20:33 Heiner Kallweit [this message]
2025-05-17 20:34 ` [PATCH net-next 1/3] net: phy: fixed_phy: remove irq argument from fixed_phy_add Heiner Kallweit
2025-05-20 7:21 ` Simon Horman
2025-05-20 17:57 ` Florian Fainelli
2025-05-20 23:29 ` Greg Ungerer
2025-05-17 20:35 ` [PATCH net-next 2/3] net: phy: fixed_phy: remove irq argument from fixed_phy_register Heiner Kallweit
2025-05-20 7:21 ` Simon Horman
2025-05-20 17:59 ` Florian Fainelli
2025-05-21 1:20 ` [PATCH net-next 0/3] net: phy: fixed_phy: simplifications and improvements 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=4d4c468e-300d-42c7-92a1-eabbdb6be748@gmail.com \
--to=hkallweit1@gmail.com \
--cc=Rengarajan.S@microchip.com \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=geert@linux-m68k.org \
--cc=gerg@linux-m68k.org \
--cc=hauke@hauke-m.de \
--cc=kuba@kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=opendmb@gmail.com \
--cc=pabeni@redhat.com \
--cc=tsbogend@alpha.franken.de \
--cc=zajec5@gmail.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).