From: patchwork-bot+netdevbpf@kernel.org
To: Aleksandr Mishin <amishin@t-argos.ru>
Cc: igal.liberman@freescale.com, horms@kernel.org,
madalin.bucur@nxp.com, sean.anderson@seco.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH net 0/2] fsl/fman: Fix refcount handling of fman-related devices
Date: Mon, 21 Oct 2024 09:20:29 +0000 [thread overview]
Message-ID: <172950242900.181020.3714375774039373979.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241015060122.25709-1-amishin@t-argos.ru>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 15 Oct 2024 09:01:20 +0300 you wrote:
> The series is intended to fix refcount handling for fman-related "struct
> device" objects - the devices are not released upon driver removal or in
> the error paths during probe. This leads to device reference leaks.
>
> The device pointers are now saved to struct mac_device and properly handled
> in the driver's probe and removal functions.
>
> [...]
Here is the summary with links:
- [net,1/2] fsl/fman: Save device references taken in mac_probe()
https://git.kernel.org/netdev/net/c/efeddd552ec6
- [net,2/2] fsl/fman: Fix refcount handling of fman-related devices
https://git.kernel.org/netdev/net/c/1dec67e0d9fb
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:[~2024-10-21 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 6:01 Aleksandr Mishin
2024-10-15 6:01 ` [PATCH net 1/2] fsl/fman: Save device references taken in mac_probe() Aleksandr Mishin
2024-10-15 6:01 ` [PATCH net 2/2] fsl/fman: Fix refcount handling of fman-related devices Aleksandr Mishin
2024-10-17 10:01 ` Paolo Abeni
2024-10-17 10:53 ` Aleksandr Mishin
2024-10-21 9:20 ` 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=172950242900.181020.3714375774039373979.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amishin@t-argos.ru \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=igal.liberman@freescale.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=madalin.bucur@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.anderson@seco.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®