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-next v2 0/2] r8152: reduce control transfer
Date: Sat, 29 Jul 2023 01:10:21 +0000 [thread overview]
Message-ID: <169059302149.26009.9262284677356277688.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230726030808.9093-417-nic_swsd@realtek.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Jul 2023 11:08:06 +0800 you wrote:
> v2:
> For patch #1, fix the typo of the commit message.
>
> v1:
> The two patches are used to reduce the number of control transfer when
> access the registers in bulk.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] r8152: adjust generic_ocp_write function
https://git.kernel.org/netdev/net-next/c/57df0fb9d511
- [net-next,v2,2/2] r8152: set bp in bulk
https://git.kernel.org/netdev/net-next/c/e5c266a61186
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-07-29 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 3:08 [PATCH net-next v2 0/2] r8152: reduce control transfer Hayes Wang
2023-07-26 3:08 ` [PATCH net-next v2 1/2] r8152: adjust generic_ocp_write function Hayes Wang
2023-07-26 8:36 ` Andrew Lunn
2023-07-26 9:50 ` Hayes Wang
2023-07-26 3:08 ` [PATCH net-next v2 2/2] r8152: set bp in bulk Hayes Wang
2023-07-26 8:39 ` Andrew Lunn
2023-07-26 9:50 ` Hayes Wang
2023-07-29 1: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=169059302149.26009.9262284677356277688.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;
as well as URLs for NNTP newsgroup(s).