From: patchwork-bot+netdevbpf@kernel.org
To: Javen <javen_xu@realsil.com.cn>
Cc: hkallweit1@gmail.com, nic_swsd@realtek.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@armlinux.org.uk
Subject: Re: [PATCH net-next v16 0/7] r8169: add RSS support for RTL8127
Date: Mon, 19 Oct 2026 23:20:07 +0000 [thread overview]
Message-ID: <179245200728.3379641.6632488338806435429.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261008065722.1026-1-javen_xu@realsil.com.cn>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 Oct 2026 14:57:15 +0800 you wrote:
> From: Javen Xu <javen_xu@realsil.com.cn>
>
> This patch series adds RSS (Receive Side Scaling) support for the r8169
> ethernet driver, specifically for RTL8127 (RTL_GIGA_MAC_VER_80).
>
> RSS enables packet distribution across multiple receive queues, which can
> significantly improve network throughput on multi-core systems by allowing
> parallel processing of incoming packets.
>
> [...]
Here is the summary with links:
- [net-next,v16,1/7] r8169: prepare for multi irqs and napi
https://git.kernel.org/netdev/net-next/c/36af5aac9545
- [net-next,v16,2/7] r8169: refactor RX path to prepare for multi-queue
https://git.kernel.org/netdev/net-next/c/5df447aee076
- [net-next,v16,3/7] r8169: add support for new interrupt mapping
https://git.kernel.org/netdev/net-next/c/677f8f8c4c5f
- [net-next,v16,4/7] r8169: prepare for new interrupt mapping
https://git.kernel.org/netdev/net-next/c/7c543c5d12b2
- [net-next,v16,5/7] r8169: add support and enable rss
https://git.kernel.org/netdev/net-next/c/90d0cfb577db
- [net-next,v16,6/7] r8169: move struct ethtool_ops
https://git.kernel.org/netdev/net-next/c/dcad1105f164
- [net-next,v16,7/7] r8169: add get_channel support for ethtool
https://git.kernel.org/netdev/net-next/c/aaf99d89a72a
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:[~2026-10-19 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 6:57 javen
2026-10-08 6:57 ` [PATCH net-next v16 1/7] r8169: prepare for multi irqs and napi javen
2026-10-08 6:57 ` [PATCH net-next v16 2/7] r8169: refactor RX path to prepare for multi-queue javen
2026-10-08 6:57 ` [PATCH net-next v16 3/7] r8169: add support for new interrupt mapping javen
2026-10-12 7:41 ` netdev-bot+sashiko
2026-10-08 6:57 ` [PATCH net-next v16 4/7] r8169: prepare " javen
2026-10-12 7:41 ` netdev-bot+sashiko
2026-10-08 6:57 ` [PATCH net-next v16 5/7] r8169: add support and enable rss javen
2026-10-12 7:41 ` netdev-bot+sashiko
2026-10-08 6:57 ` [PATCH net-next v16 6/7] r8169: move struct ethtool_ops javen
2026-10-08 6:57 ` [PATCH net-next v16 7/7] r8169: add get_channel support for ethtool javen
2026-10-19 23: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=179245200728.3379641.6632488338806435429.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=javen_xu@realsil.com.cn \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®