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
Subject: Re: [PATCH net v3 0/3] r8152: fix 2.5G devices
Date: Mon, 01 May 2023 06:40:20 +0000 [thread overview]
Message-ID: <168292322069.19130.7182582489809893129.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230428085331.34550-409-nic_swsd@realtek.com>
Hello:
This series was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 28 Apr 2023 16:53:28 +0800 you wrote:
> v3:
> For patch #2, modify the comment.
>
> v2:
> For patch #1, Remove inline for fc_pause_on_auto() and fc_pause_off_auto(),
> and update the commit message.
>
> [...]
Here is the summary with links:
- [net,v3,1/3] r8152: fix flow control issue of RTL8156A
https://git.kernel.org/netdev/net/c/8ceda6d5a1e5
- [net,v3,2/3] r8152: fix the poor throughput for 2.5G devices
https://git.kernel.org/netdev/net/c/61b0ad6f58e2
- [net,v3,3/3] r8152: move setting r8153b_rx_agg_chg_indicate()
https://git.kernel.org/netdev/net/c/cce8334f4aac
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-05-01 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 8:53 Hayes Wang
2023-04-28 8:53 ` [PATCH net v3 1/3] r8152: fix flow control issue of RTL8156A Hayes Wang
2023-04-28 8:53 ` [PATCH net v3 2/3] r8152: fix the poor throughput for 2.5G devices Hayes Wang
2023-04-28 20:02 ` Andrew Lunn
2023-04-28 8:53 ` [PATCH net v3 3/3] r8152: move setting r8153b_rx_agg_chg_indicate() Hayes Wang
2023-05-01 6: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=168292322069.19130.7182582489809893129.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--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 \
/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®