From: patchwork-bot+netdevbpf@kernel•org
To: Lorenzo Bianconi <lorenzo@kernel•org>
Cc: netdev@vger•kernel.org, lorenzo.bianconi@redhat•com,
bpf@vger•kernel.org, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, hawk@kernel•org,
john.fastabend@gmail•com, linyunsheng@huawei•com, ast@kernel•org,
daniel@iogearbox•net, jbenc@redhat•com
Subject: Re: [PATCH net-next] net: veth: make PAGE_POOL_STATS optional
Date: Wed, 10 May 2023 09:00:22 +0000 [thread overview]
Message-ID: <168370922281.25656.18183130593399665986.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <c9e132c3f08c456ad0462342bb0a104f0f8c0b24.1683622992.git.lorenzo@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft•net>:
On Tue, 9 May 2023 11:05:16 +0200 you wrote:
> Since veth is very likely to be enabled and there are some drivers
> (e.g. mlx5) where CONFIG_PAGE_POOL_STATS is optional, make
> CONFIG_PAGE_POOL_STATS optional for veth too in order to keep it
> optional when required.
>
> Suggested-by: Jiri Benc <jbenc@redhat•com>
> Signed-off-by: Lorenzo Bianconi <lorenzo@kernel•org>
>
> [...]
Here is the summary with links:
- [net-next] net: veth: make PAGE_POOL_STATS optional
https://git.kernel.org/netdev/net-next/c/5e316a818e75
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-10 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 9:05 [PATCH net-next] net: veth: make PAGE_POOL_STATS optional Lorenzo Bianconi
2023-05-09 10:21 ` Simon Horman
2023-05-09 11:08 ` Jesper Dangaard Brouer
2023-05-09 12:10 ` Toke Høiland-Jørgensen
2023-05-10 9:00 ` 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=168370922281.25656.18183130593399665986.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=jbenc@redhat$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linyunsheng@huawei$(echo .)com \
--cc=lorenzo.bianconi@redhat$(echo .)com \
--cc=lorenzo@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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