From: patchwork-bot+netdevbpf@kernel.org
To: Russell King (Oracle) <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, davem@davemloft.net,
edumazet@google.com, ioana.ciornei@nxp.com, kuba@kernel.org,
madalin.bucur@nxp.com, netdev@vger.kernel.org, pabeni@redhat.com,
sean.anderson@seco.com
Subject: Re: [PATCH net-next v2 00/11] complete Lynx mdio device handling
Date: Fri, 09 Jun 2023 02:30:23 +0000 [thread overview]
Message-ID: <168627782387.6230.14795941362471671231.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ZIBwuw+IuGQo5yV8@shell.armlinux.org.uk>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 7 Jun 2023 12:57:47 +0100 you wrote:
> Hi,
>
> This series completes the mdio device lifetime handling for Lynx PCS
> users which do not create their own mdio device, but instead fetch
> it using a firmware description - namely the DPAA2 and FMAN_MEMAC
> drivers.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/11] net: dpaa2-mac: allow lynx PCS to manage mdiodev lifetime
https://git.kernel.org/netdev/net-next/c/6c79a9c8b1f3
- [net-next,v2,02/11] net: fman_memac: allow lynx PCS to handle mdiodev lifetime
https://git.kernel.org/netdev/net-next/c/d7b6ea1a14e4
- [net-next,v2,03/11] net: pcs: lynx: remove lynx_get_mdio_device()
https://git.kernel.org/netdev/net-next/c/b3b984dc0ba6
- [net-next,v2,04/11] net: pcs: lynx: add lynx_pcs_create_fwnode()
https://git.kernel.org/netdev/net-next/c/6e1a12821d34
- [net-next,v2,05/11] net: dpaa2-mac: use lynx_pcs_create_fwnode()
https://git.kernel.org/netdev/net-next/c/595fa7634d71
- [net-next,v2,06/11] net: fman_memac: use lynx_pcs_create_fwnode()
https://git.kernel.org/netdev/net-next/c/929a629c211f
- [net-next,v2,07/11] net: pcs: lynx: make lynx_pcs_create() static
https://git.kernel.org/netdev/net-next/c/84e476b876d9
- [net-next,v2,08/11] net: pcs: lynx: change lynx_pcs_create() to return error-pointers
https://git.kernel.org/netdev/net-next/c/05b606b88452
- [net-next,v2,09/11] net: pcs: lynx: check that the fwnode is available prior to use
https://git.kernel.org/netdev/net-next/c/d143898c6d7b
- [net-next,v2,10/11] net: dpaa2: use pcs-lynx's check for fwnode availability
https://git.kernel.org/netdev/net-next/c/8c1d0b339d67
- [net-next,v2,11/11] net: fman_memac: use pcs-lynx's check for fwnode availability
https://git.kernel.org/netdev/net-next/c/32fc30353f7c
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:[~2023-06-09 2:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 11:57 [PATCH net-next v2 00/11] complete Lynx mdio device handling Russell King (Oracle)
2023-06-07 11:58 ` [PATCH net-next v2 01/11] net: dpaa2-mac: allow lynx PCS to manage mdiodev lifetime Russell King (Oracle)
2023-06-07 11:58 ` [PATCH net-next v2 02/11] net: fman_memac: allow lynx PCS to handle " Russell King (Oracle)
2023-06-07 11:58 ` [PATCH net-next v2 03/11] net: pcs: lynx: remove lynx_get_mdio_device() Russell King (Oracle)
2023-06-07 11:58 ` [PATCH net-next v2 04/11] net: pcs: lynx: add lynx_pcs_create_fwnode() Russell King (Oracle)
2023-06-07 11:58 ` [PATCH net-next v2 05/11] net: dpaa2-mac: use lynx_pcs_create_fwnode() Russell King (Oracle)
2023-06-07 11:58 ` [PATCH net-next v2 06/11] net: fman_memac: " Russell King (Oracle)
2023-06-07 11:58 ` [PATCH net-next v2 07/11] net: pcs: lynx: make lynx_pcs_create() static Russell King (Oracle)
2023-06-07 11:58 ` [PATCH net-next v2 08/11] net: pcs: lynx: change lynx_pcs_create() to return error-pointers Russell King (Oracle)
2023-06-07 11:58 ` [PATCH net-next v2 09/11] net: pcs: lynx: check that the fwnode is available prior to use Russell King (Oracle)
2023-06-07 11:58 ` [PATCH net-next v2 10/11] net: dpaa2: use pcs-lynx's check for fwnode availability Russell King (Oracle)
2023-06-07 11:59 ` [PATCH net-next v2 11/11] net: fman_memac: " Russell King (Oracle)
2023-06-09 2:30 ` 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=168627782387.6230.14795941362471671231.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.anderson@seco.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).