From: patchwork-bot+netdevbpf@kernel.org
To: Hayes Wang <hayeswang@realtek.com>
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
nic_swsd@realtek.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, edumazet@google.com, bjorn@mork.no,
pabeni@redhat.com
Subject: Re: [PATCH net-next v3 0/2] r8152: modify rx_bottom
Date: Thu, 05 Oct 2023 00:10:26 +0000 [thread overview]
Message-ID: <169646462631.25730.11600010674078336884.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230926111714.9448-432-nic_swsd@realtek.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 26 Sep 2023 19:17:12 +0800 you wrote:
> v3:
> For patch #1, this patch is replaced. The new patch only break the loop,
> and keep that the driver would queue the rx packets.
>
> For patch #2, modify the code depends on patch #1. For work_down < budget,
> napi_get_frags() and napi_gro_frags() would be used. For the others,
> nothing is changed.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] r8152: break the loop when the budget is exhausted
https://git.kernel.org/netdev/net-next/c/2cf51f931797
- [net-next,v3,2/2] r8152: use napi_gro_frags
https://git.kernel.org/netdev/net-next/c/788d30daa8f9
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-10-05 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 11:17 Hayes Wang
2023-09-26 11:17 ` [PATCH net-next v3 1/2] r8152: break the loop when the budget is exhausted Hayes Wang
2023-09-26 11:17 ` [PATCH net-next v3 2/2] r8152: use napi_gro_frags Hayes Wang
2023-10-05 0:10 ` 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=169646462631.25730.11600010674078336884.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hayeswang@realtek.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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®