From: patchwork-bot+netdevbpf@kernel.org
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: netdev@vger.kernel.org, andriy.shevchenko@linux.intel.com,
Jose.Abreu@synopsys.com, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, linux-gpio@vger.kernel.org,
mengyuanlou@net-swift.com
Subject: Re: [PATCH net-next v12 0/8] TXGBE PHYLINK support
Date: Thu, 08 Jun 2023 11:40:22 +0000 [thread overview]
Message-ID: <168622442263.17370.16554373092861552237.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230606092107.764621-1-jiawenwu@trustnetic.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 6 Jun 2023 17:20:59 +0800 you wrote:
> Implement I2C, SFP, GPIO and PHYLINK to setup TXGBE link.
>
> Because our I2C and PCS are based on Synopsys Designware IP-core, extend
> the i2c-designware and pcs-xpcs driver to realize our functions.
>
> v11 -> v12:
> - split I2C designware patch (2/9) to I2C tree, repost remaining 8
> patches
>
> [...]
Here is the summary with links:
- [net-next,v12,1/8] net: txgbe: Add software nodes to support phylink
https://git.kernel.org/netdev/net-next/c/c3e382ad6d15
- [net-next,v12,2/8] net: txgbe: Register fixed rate clock
https://git.kernel.org/netdev/net-next/c/b63f20485e43
- [net-next,v12,3/8] net: txgbe: Register I2C platform device
https://git.kernel.org/netdev/net-next/c/c625e72561f6
- [net-next,v12,4/8] net: txgbe: Add SFP module identify
https://git.kernel.org/netdev/net-next/c/04d94236182e
- [net-next,v12,5/8] net: txgbe: Support GPIO to SFP socket
https://git.kernel.org/netdev/net-next/c/b83c37315a62
- [net-next,v12,6/8] net: pcs: Add 10GBASE-R mode for Synopsys Designware XPCS
https://git.kernel.org/netdev/net-next/c/af8de1e307bf
- [net-next,v12,7/8] net: txgbe: Implement phylink pcs
https://git.kernel.org/netdev/net-next/c/854cace61387
- [net-next,v12,8/8] net: txgbe: Support phylink MAC layer
https://git.kernel.org/netdev/net-next/c/08f08f9390e4
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-08 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 9:20 [PATCH net-next v12 0/8] TXGBE PHYLINK support Jiawen Wu
2023-06-06 9:21 ` [PATCH net-next v12 1/8] net: txgbe: Add software nodes to support phylink Jiawen Wu
2023-06-06 9:21 ` [PATCH net-next v12 2/8] net: txgbe: Register fixed rate clock Jiawen Wu
2023-06-06 9:21 ` [PATCH net-next v12 3/8] net: txgbe: Register I2C platform device Jiawen Wu
2023-06-06 9:21 ` [PATCH net-next v12 4/8] net: txgbe: Add SFP module identify Jiawen Wu
2023-06-06 9:21 ` [PATCH net-next v12 5/8] net: txgbe: Support GPIO to SFP socket Jiawen Wu
2023-06-06 9:21 ` [PATCH net-next v12 6/8] net: pcs: Add 10GBASE-R mode for Synopsys Designware XPCS Jiawen Wu
2023-06-06 9:21 ` [PATCH net-next v12 7/8] net: txgbe: Implement phylink pcs Jiawen Wu
2023-06-06 9:21 ` [PATCH net-next v12 8/8] net: txgbe: Support phylink MAC layer Jiawen Wu
2023-06-06 18:19 ` [PATCH net-next v12 0/8] TXGBE PHYLINK support Maciej Fijalkowski
2023-06-08 11:40 ` 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=168622442263.17370.16554373092861552237.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jose.Abreu@synopsys.com \
--cc=andrew@lunn.ch \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hkallweit1@gmail.com \
--cc=jiawenwu@trustnetic.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mengyuanlou@net-swift.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.