From: patchwork-bot+netdevbpf@kernel.org
To: huangguangbin (A) <huangguangbin2@huawei.com>
Cc: mkubecek@suse.cz, davem@davemloft.net, kuba@kernel.org,
netdev@vger.kernel.org, lipeng321@huawei.com
Subject: Re: [PATCH ethtool-next v3 0/2] Add support to get/set tx push by ethtool -G/g
Date: Sun, 08 May 2022 20:50:12 +0000 [thread overview]
Message-ID: <165204301264.30767.10690359782009256931.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220429091704.21258-1-huangguangbin2@huawei.com>
Hello:
This series was applied to ethtool/ethtool.git (next)
by Michal Kubecek <mkubecek@suse.cz>:
On Fri, 29 Apr 2022 17:17:02 +0800 you wrote:
> From: Jie Wang <wangjie125@huawei.com>
>
> These two patches first update uapi headers by using the import shell, then
> add support to get/set tx push by ethtool -G/g.
>
> Changelog:
> v2->v3
> 1.Revise the min_argc value of tx-push.
> link:https://lore.kernel.org/netdev/20220421084646.15458-1-huangguangbin2@huawei.com/
>
> [...]
Here is the summary with links:
- [ethtool-next,v3,1/2] update UAPI header copies
https://git.kernel.org/pub/scm/network/ethtool/ethtool.git/commit/?id=bd138ee083c4
- [ethtool-next,v3,2/2] ethtool: add support to get/set tx push by ethtool -G/g
(no matching commit)
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:[~2022-05-08 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 9:17 [PATCH ethtool-next v3 0/2] Add support to get/set tx push by ethtool -G/g Guangbin Huang
2022-04-29 9:17 ` [PATCH ethtool-next v3 1/2] update UAPI header copies Guangbin Huang
2022-04-29 9:17 ` [PATCH ethtool-next v3 2/2] ethtool: add support to get/set tx push by ethtool -G/g Guangbin Huang
2022-05-08 20:50 ` 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=165204301264.30767.10690359782009256931.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=kuba@kernel.org \
--cc=lipeng321@huawei.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
/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).