From: patchwork-bot+netdevbpf@kernel.org
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: netdev@vger.kernel.org, lorenzo.bianconi@redhat.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
thomas.petazzoni@bootlin.com, ilias.apalodimas@linaro.org,
jbrouer@redhat.com, andrew@lunn.ch, jdamato@fastly.com
Subject: Re: [PATCH v5 net-next 0/2] net: mvneta: add support for page_pool_get_stats
Date: Fri, 15 Apr 2022 09:50:11 +0000 [thread overview]
Message-ID: <165001621118.31041.3013313309484609030.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1649780789.git.lorenzo@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 12 Apr 2022 18:31:57 +0200 you wrote:
> Introduce page_pool stats ethtool APIs in order to avoid driver duplicated
> code.
>
> Changes since v4:
> - rebase on top of net-next
>
> Changes since v3:
> - get rid of wrong for loop in page_pool_ethtool_stats_get()
> - add API stubs when page_pool_stats are not compiled in
>
> [...]
Here is the summary with links:
- [v5,net-next,1/2] net: page_pool: introduce ethtool stats
https://git.kernel.org/netdev/net-next/c/f3c5264f452a
- [v5,net-next,2/2] net: mvneta: add support for page_pool_get_stats
https://git.kernel.org/netdev/net-next/c/b3fc79225f05
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-04-15 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 16:31 [PATCH v5 net-next 0/2] net: mvneta: add support for page_pool_get_stats Lorenzo Bianconi
2022-04-12 16:31 ` [PATCH v5 net-next 1/2] net: page_pool: introduce ethtool stats Lorenzo Bianconi
2022-04-14 11:17 ` Jakub Kicinski
2022-04-14 22:10 ` Ilias Apalodimas
2022-04-12 16:31 ` [PATCH v5 net-next 2/2] net: mvneta: add support for page_pool_get_stats Lorenzo Bianconi
2022-04-15 9: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=165001621118.31041.3013313309484609030.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=ilias.apalodimas@linaro.org \
--cc=jbrouer@redhat.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.