From: patchwork-bot+netdevbpf@kernel•org
To: Liang Chen <liangchen.linux@gmail•com>
Cc: hawk@kernel•org, horms@kernel•org, davem@davemloft•net,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
linyunsheng@huawei•com, ilias.apalodimas@linaro•org,
daniel@iogearbox•net, ast@kernel•org, netdev@vger•kernel.org
Subject: Re: [PATCH net-next v2] net: veth: Page pool creation error handling for existing pools only
Date: Tue, 15 Aug 2023 02:30:19 +0000 [thread overview]
Message-ID: <169206661942.16325.9389282746030868287.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230812023016.10553-1-liangchen.linux@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Sat, 12 Aug 2023 10:30:16 +0800 you wrote:
> The failure handling procedure destroys page pools for all queues,
> including those that haven't had their page pool created yet. this patch
> introduces necessary adjustments to prevent potential risks and
> inconsistency with the error handling behavior.
>
> Fixes: 0ebab78cbcbf ("net: veth: add page_pool for page recycling")
> Acked-by: Jesper Dangaard Brouer <hawk@kernel•org>
> Signed-off-by: Liang Chen <liangchen.linux@gmail•com>
>
> [...]
Here is the summary with links:
- [net-next,v2] net: veth: Page pool creation error handling for existing pools only
https://git.kernel.org/netdev/net/c/8a519a572598
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-08-15 2:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-12 2:30 [PATCH net-next v2] net: veth: Page pool creation error handling for existing pools only Liang Chen
2023-08-15 2:30 ` 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=169206661942.16325.9389282746030868287.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hawk@kernel$(echo .)org \
--cc=horms@kernel$(echo .)org \
--cc=ilias.apalodimas@linaro$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=liangchen.linux@gmail$(echo .)com \
--cc=linyunsheng@huawei$(echo .)com \
--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