From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: gerg@linux-m68k.org, geert@linux-m68k.org, hauke@hauke-m.de,
zajec5@gmail.com, tsbogend@alpha.franken.de, olteanv@gmail.com,
opendmb@gmail.com, florian.fainelli@broadcom.com,
Thangaraj.S@microchip.com, Rengarajan.S@microchip.com,
UNGLinuxDriver@microchip.com, andrew@lunn.ch,
andrew+netdev@lunn.ch, linux@armlinux.org.uk,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, bcm-kernel-feedback-list@broadcom.com,
linux-m68k@lists.linux-m68k.org, linux-mips@vger.kernel.org,
linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: phy: fixed_phy: simplifications and improvements
Date: Wed, 21 May 2025 01:20:50 +0000 [thread overview]
Message-ID: <174779045049.1526198.18389815848433022265.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <4d4c468e-300d-42c7-92a1-eabbdb6be748@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 17 May 2025 22:33:23 +0200 you wrote:
> 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
>
> [...]
Here is the summary with links:
- [net-next,1/3] net: phy: fixed_phy: remove irq argument from fixed_phy_add
https://git.kernel.org/netdev/net-next/c/3f1716ee0f6c
- [net-next,2/3] net: phy: fixed_phy: remove irq argument from fixed_phy_register
https://git.kernel.org/netdev/net-next/c/d23b4af5df39
- [net-next,3/3] net: phy: fixed_phy: constify status argument where possible
https://git.kernel.org/netdev/net-next/c/4ba1c5bb4811
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-05-21 1:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 20:33 [PATCH net-next 0/3] net: phy: fixed_phy: simplifications and improvements Heiner Kallweit
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 ` patchwork-bot+netdevbpf [this message]
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=174779045049.1526198.18389815848433022265.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--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=hkallweit1@gmail.com \
--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