public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Petko Manolov <petko.manolov@konsulko.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	stable@vger.kernel.org, pabeni@redhat.com, andrew@lunn.ch,
	petkan@nucleusys.com
Subject: Re: [PATCH NET v2 1/1] net: usb: pegasus: fix memory leak in update_eth_regs_async()
Date: Thu, 08 Jan 2026 16:50:22 +0000	[thread overview]
Message-ID: <176789102277.3716059.3717751225941024809.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260106084821.3746677-1-petko.manolov@konsulko.com>

Hello:

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

On Tue,  6 Jan 2026 10:48:21 +0200 you wrote:
> From: Petko Manolov <petkan@nucleusys.com>
> 
> When asynchronously writing to the device registers and if usb_submit_urb()
> fail, the code fail to release allocated to this point resources.
> 
> Fixes: 323b34963d11 ("drivers: net: usb: pegasus: fix control urb submission")
> Signed-off-by: Petko Manolov <petkan@nucleusys.com>
> 
> [...]

Here is the summary with links:
  - [NET,v2,1/1] net: usb: pegasus: fix memory leak in update_eth_regs_async()
    https://git.kernel.org/netdev/net/c/afa27621a28a

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



      reply	other threads:[~2026-01-08 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06  8:48 [PATCH NET v2 1/1] net: usb: pegasus: fix memory leak in update_eth_regs_async() Petko Manolov
2026-01-08 16:50 ` 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=176789102277.3716059.3717751225941024809.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petkan@nucleusys.com \
    --cc=petko.manolov@konsulko.com \
    --cc=stable@vger.kernel.org \
    /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