From: patchwork-bot+netdevbpf@kernel.org
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linux@armlinux.org.uk, andrew@lunn.ch,
netdev@vger.kernel.org, mengyuanlou@net-swift.com
Subject: Re: [PATCH net-next v7 0/8] Implement more ethtool_ops for Wangxun
Date: Thu, 04 Jan 2024 11:00:28 +0000 [thread overview]
Message-ID: <170436602866.13188.11364431731161025698.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240103020854.1656604-1-jiawenwu@trustnetic.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 3 Jan 2024 10:08:46 +0800 you wrote:
> Provide ethtool functions to operate pause param, ring param, coalesce
> channel number and msglevel, for driver txgbe/ngbe.
>
> v6 -> v7:
> - Rebase on net-next.
>
> v5 -> v6:
> - Minor fixes address on Jakub Kicinski's comments.
>
> [...]
Here is the summary with links:
- [net-next,v7,1/8] net: libwx: add phylink to libwx
https://git.kernel.org/netdev/net-next/c/e8e138cf7383
- [net-next,v7,2/8] net: txgbe: use phylink bits added in libwx
https://git.kernel.org/netdev/net-next/c/4491c602fe5f
- [net-next,v7,3/8] net: ngbe: convert phylib to phylink
https://git.kernel.org/netdev/net-next/c/bc2426d74aa3
- [net-next,v7,4/8] net: wangxun: add flow control support
https://git.kernel.org/netdev/net-next/c/2fe2ca09da95
- [net-next,v7,5/8] net: wangxun: add ethtool_ops for ring parameters
https://git.kernel.org/netdev/net-next/c/883b5984a5d2
- [net-next,v7,6/8] net: wangxun: add coalesce options support
https://git.kernel.org/netdev/net-next/c/4ac2d9dff4b0
- [net-next,v7,7/8] net: wangxun: add ethtool_ops for channel number
https://git.kernel.org/netdev/net-next/c/937d46ecc5f9
- [net-next,v7,8/8] net: wangxun: add ethtool_ops for msglevel
https://git.kernel.org/netdev/net-next/c/b746dc6bdde5
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:[~2024-01-04 11:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 2:08 [PATCH net-next v7 0/8] Implement more ethtool_ops for Wangxun Jiawen Wu
2024-01-03 2:08 ` [PATCH net-next v7 1/8] net: libwx: add phylink to libwx Jiawen Wu
2024-01-03 14:30 ` Russell King (Oracle)
2024-01-03 2:08 ` [PATCH net-next v7 2/8] net: txgbe: use phylink bits added in libwx Jiawen Wu
2024-01-03 14:32 ` Russell King (Oracle)
2024-01-03 2:08 ` [PATCH net-next v7 3/8] net: ngbe: convert phylib to phylink Jiawen Wu
2024-01-03 14:35 ` Russell King (Oracle)
2024-01-03 2:08 ` [PATCH net-next v7 4/8] net: wangxun: add flow control support Jiawen Wu
2024-01-03 14:48 ` Russell King (Oracle)
2024-01-03 2:08 ` [PATCH net-next v7 5/8] net: wangxun: add ethtool_ops for ring parameters Jiawen Wu
2024-01-03 2:08 ` [PATCH net-next v7 6/8] net: wangxun: add coalesce options support Jiawen Wu
2024-01-03 2:08 ` [PATCH net-next v7 7/8] net: wangxun: add ethtool_ops for channel number Jiawen Wu
2024-01-03 2:08 ` [PATCH net-next v7 8/8] net: wangxun: add ethtool_ops for msglevel Jiawen Wu
2024-01-04 11:00 ` 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=170436602866.13188.11364431731161025698.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiawenwu@trustnetic.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mengyuanlou@net-swift.com \
--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 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.