From: patchwork-bot+netdevbpf@kernel.org
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, michal.kubiak@intel.com,
mengyuanlou@net-swift.com, duanqiangwen@net-swift.com
Subject: Re: [PATCH net v2 0/3] Fix Rx fatal errors
Date: Wed, 16 Jul 2025 00:40:17 +0000 [thread overview]
Message-ID: <175262641799.629458.8420167571030226801.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250714024755.17512-1-jiawenwu@trustnetic.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 14 Jul 2025 10:47:52 +0800 you wrote:
> There are some fatal errors on the Rx NAPI path, which can cause the
> kernel to crash. Fix known issues and potential risks.
>
> The part of the patches has been mentioned before[1].
>
> [1]: https://lore.kernel.org/all/C8A23A11DB646E60+20250630094102.22265-1-jiawenwu@trustnetic.com/
>
> [...]
Here is the summary with links:
- [net,v2,1/3] net: libwx: remove duplicate page_pool_put_full_page()
https://git.kernel.org/netdev/net/c/1b7e585c04cd
- [net,v2,2/3] net: libwx: fix the using of Rx buffer DMA
https://git.kernel.org/netdev/net/c/5fd77cc6bd9b
- [net,v2,3/3] net: libwx: properly reset Rx ring descriptor
https://git.kernel.org/netdev/net/c/d992ed7e1b68
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:[~2025-07-16 0:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 2:47 [PATCH net v2 0/3] Fix Rx fatal errors Jiawen Wu
2025-07-14 2:47 ` [PATCH net v2 1/3] net: libwx: remove duplicate page_pool_put_full_page() Jiawen Wu
2025-07-14 11:11 ` Simon Horman
2025-07-14 2:47 ` [PATCH net v2 2/3] net: libwx: fix the using of Rx buffer DMA Jiawen Wu
2025-07-14 2:47 ` [PATCH net v2 3/3] net: libwx: properly reset Rx ring descriptor Jiawen Wu
2025-07-16 0: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=175262641799.629458.8420167571030226801.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=duanqiangwen@net-swift.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiawenwu@trustnetic.com \
--cc=kuba@kernel.org \
--cc=mengyuanlou@net-swift.com \
--cc=michal.kubiak@intel.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.