All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Cosmin Ratiu <cratiu@nvidia.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	horms@kernel.org, michal.wilczynski@intel.com,
	cjubran@nvidia.com, mbloch@nvidia.com, tariqt@nvidia.com
Subject: Re: [PATCH net 0/2] devlink: Fix a couple parent ref leaks
Date: Fri, 19 Jun 2026 01:10:13 +0000	[thread overview]
Message-ID: <178183141314.3148637.4107532095640365241.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260616110633.1449432-1-cratiu@nvidia.com>

Hello:

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

On Tue, 16 Jun 2026 14:06:31 +0300 you wrote:
> These two patches fix parent ref leaks on errors.
> 
> Cosmin Ratiu (2):
>   devlink: Fix parent ref leak in devl_rate_node_create()
>   devlink: Fix parent ref leak on tc-bw failure
> 
>  net/devlink/rate.c | 25 ++++++++++++++-----------
>  1 file changed, 14 insertions(+), 11 deletions(-)

Here is the summary with links:
  - [net,1/2] devlink: Fix parent ref leak in devl_rate_node_create()
    https://git.kernel.org/netdev/net/c/ba45106342bb
  - [net,2/2] devlink: Fix parent ref leak on tc-bw failure
    https://git.kernel.org/netdev/net/c/ba81a8b80f04

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



      parent reply	other threads:[~2026-06-19  1:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 11:06 [PATCH net 0/2] devlink: Fix a couple parent ref leaks Cosmin Ratiu
2026-06-16 11:06 ` [PATCH net 1/2] devlink: Fix parent ref leak in devl_rate_node_create() Cosmin Ratiu
2026-06-16 11:06 ` [PATCH net 2/2] devlink: Fix parent ref leak on tc-bw failure Cosmin Ratiu
2026-06-17 14:02 ` [PATCH net 0/2] devlink: Fix a couple parent ref leaks Simon Horman
2026-06-19  1: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=178183141314.3148637.4107532095640365241.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=cjubran@nvidia.com \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=michal.wilczynski@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tariqt@nvidia.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.