From: patchwork-bot+netdevbpf@kernel.org
To: Dan Jurgens <danielj@nvidia.com>
Cc: netdev@vger.kernel.org, mst@redhat.com, jasowang@redhat.com,
xuanzhuo@linux.alibaba.com, virtualization@lists.linux.dev,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jiri@nvidia.com
Subject: Re: [PATCH net-next 0/2] Add TX stop/wake counters
Date: Mon, 13 May 2024 22:50:28 +0000 [thread overview]
Message-ID: <171564062896.28873.12862899277990003394.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240510201927.1821109-1-danielj@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 10 May 2024 23:19:25 +0300 you wrote:
> Several drivers provide TX stop and wake counters via ethtool stats. Add
> those to the netdev queue stats, and use them in virtio_net.
>
> v2:
> - Fixed an accidental line deletion
> - Enhanced documentation
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] netdev: Add queue stats for TX stop and wake
https://git.kernel.org/netdev/net-next/c/b56035101e1c
- [net-next,v2,2/2] virtio_net: Add TX stopped and wake counters
https://git.kernel.org/netdev/net-next/c/c39add9b2423
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2024-05-13 22:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 20:19 [PATCH net-next 0/2] Add TX stop/wake counters Daniel Jurgens
2024-05-10 20:19 ` [PATCH net-next v2 1/2] netdev: Add queue stats for TX stop and wake Daniel Jurgens
2024-05-11 3:31 ` Jason Xing
2024-05-10 20:19 ` [PATCH net-next v2 2/2] virtio_net: Add TX stopped and wake counters Daniel Jurgens
2024-05-11 3:38 ` Jason Xing
2024-05-13 22:50 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-09 16:32 [PATCH net-next 0/2] Add TX stop/wake counters Daniel Jurgens
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=171564062896.28873.12862899277990003394.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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 read-only IMAP folder(s) and NNTP newsgroup(s).