From: patchwork-bot+netdevbpf@kernel.org
To: Guangshuo Li <lgs201920130244@gmail.com>
Cc: akiyano@amazon.com, darinzon@amazon.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, ioana.ciornei@nxp.com, ekffu200098@gmail.com,
dawei.feng@seu.edu.cn, amitbern@amazon.com,
netanel@annapurnalabs.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] net: ena: fix resource cleanup on probe failure
Date: Thu, 24 Sep 2026 17:10:09 +0000 [thread overview]
Message-ID: <179026980914.1660211.16967446500117783389.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260921154202.471662-1-lgs201920130244@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 21 Sep 2026 23:42:00 +0800 you wrote:
> This series fixes two resource leaks in the ena_probe() error path after
> ena_device_init() has successfully initialized device resources.
>
> Patch 1 adds the missing PHC cleanup.
> Patch 2 adds the missing MMIO read request cleanup.
>
> v2:
> - Resend the PHC and MMIO cleanup fixes as a two-patch series, as
> requested by Arthur Kiyanovski.
>
> [...]
Here is the summary with links:
- [v2,1/2] net: ena: fix PHC cleanup on probe failure
https://git.kernel.org/netdev/net/c/0958ea4355e2
- [v2,2/2] net: ena: fix MMIO read buffer leak on probe failure
https://git.kernel.org/netdev/net/c/9476b4468862
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:[~2026-09-24 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 15:42 Guangshuo Li
2026-09-21 15:42 ` [PATCH v2 1/2] net: ena: fix PHC " Guangshuo Li
2026-09-21 19:06 ` Arthur Kiyanovski
2026-09-21 22:02 ` Krzysztof Kozlowski
2026-09-22 2:12 ` Guangshuo Li
2026-09-23 6:42 ` netdev-bot+sashiko
2026-09-21 15:42 ` [PATCH v2 2/2] net: ena: fix MMIO read buffer leak " Guangshuo Li
2026-09-24 17:10 ` 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=179026980914.1660211.16967446500117783389.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akiyano@amazon.com \
--cc=amitbern@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=dawei.feng@seu.edu.cn \
--cc=edumazet@google.com \
--cc=ekffu200098@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netanel@annapurnalabs.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®