From: patchwork-bot+netdevbpf@kernel.org
To: Yibo Dong <dong100@mucse.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, vadim.fedorenko@linux.dev,
u.kleine-koenig@baylibre.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, yaojun@mucse.com
Subject: Re: [PATCH net-next v16 0/5] net: rnpgbe: Add TX/RX and link status support
Date: Tue, 20 Oct 2026 03:00:10 +0000 [thread overview]
Message-ID: <179246521027.3454580.12892078954545199148.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <3B42BE25B3696EAE+20261013022920.63529-1-dong100@mucse.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 13 Oct 2026 10:29:20 +0800 you wrote:
> Hi maintainers,
>
> This patch series adds the packet transmission, reception, and link status
> management features to the RNPGBE driver, building upon the previously
> introduced mailbox communication and basic driver infrastructure.
>
> The series introduces:
> - MSI-X interrupt handling with NAPI support
> - TX path with scatter-gather DMA and completion handling
> - RX path with page pool buffer management
> - Unicast/Multicast filter.
> - Firmware link-event processing and carrier management
>
> [...]
Here is the summary with links:
- [net-next,v16,1/5] net: rnpgbe: Add interrupt handling
https://git.kernel.org/netdev/net-next/c/600efa8e598c
- [net-next,v16,2/5] net: rnpgbe: Add basic TX packet transmission support
https://git.kernel.org/netdev/net-next/c/02b5891a50c1
- [net-next,v16,3/5] net: rnpgbe: Add basic RX data path support
https://git.kernel.org/netdev/net-next/c/250a6edaea49
- [net-next,v16,4/5] net: rnpgbe: Add receive mode support
https://git.kernel.org/netdev/net-next/c/20c17178e192
- [net-next,v16,5/5] net: rnpgbe: Add link status handling support
https://git.kernel.org/netdev/net-next/c/92a671d510a8
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-20 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 2:29 [PATCH net-next v16 0/5] net: rnpgbe: Add TX/RX and link status support Dong Yibo
2026-10-13 2:30 ` [PATCH net-next v16 1/5] net: rnpgbe: Add interrupt handling Dong Yibo
2026-10-14 2:59 ` netdev-bot+sashiko
2026-10-13 2:30 ` [PATCH net-next v16 2/5] net: rnpgbe: Add basic TX packet transmission support Dong Yibo
2026-10-14 2:59 ` netdev-bot+sashiko
2026-10-14 5:42 ` Yibo Dong
2026-10-13 2:30 ` [PATCH net-next v16 3/5] net: rnpgbe: Add basic RX data path support Dong Yibo
2026-10-13 2:30 ` [PATCH net-next v16 4/5] net: rnpgbe: Add receive mode support Dong Yibo
2026-10-13 2:31 ` [PATCH net-next v16 5/5] net: rnpgbe: Add link status handling support Dong Yibo
2026-10-14 2:59 ` netdev-bot+sashiko
2026-10-20 3: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=179246521027.3454580.12892078954545199148.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dong100@mucse.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vadim.fedorenko@linux.dev \
--cc=yaojun@mucse.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