All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: kuba@kernel.org, o.rempel@pengutronix.de, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com
Subject: Re: [PATCH net] net: pse-pd: pd692x0: Fix power budget leak in manager setup error path
Date: Thu, 21 Aug 2025 15:00:14 +0000	[thread overview]
Message-ID: <175578841499.1075387.3252832210144588018.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250820132708.837255-1-kory.maincent@bootlin.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 20 Aug 2025 15:27:07 +0200 you wrote:
> Fix a resource leak where manager power budgets were freed on both
> success and error paths during manager setup. Power budgets should
> only be freed on error paths after regulator registration or during
> driver removal.
> 
> Refactor cleanup logic by extracting OF node cleanup and power budget
> freeing into separate helper functions for better maintainability.
> 
> [...]

Here is the summary with links:
  - [net] net: pse-pd: pd692x0: Fix power budget leak in manager setup error path
    https://git.kernel.org/netdev/net/c/1c67f9c54cdc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-08-21 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20 13:27 [PATCH net] net: pse-pd: pd692x0: Fix power budget leak in manager setup error path Kory Maincent
2025-08-20 14:08 ` Markus Elfring
2025-08-21 15: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=175578841499.1075387.3252832210144588018.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --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.