From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
johan@kernel.org, stable@vger.kernel.org,
jakob.unterwurzacher@theobroma-systems.com
Subject: Re: [PATCH net 1/2] can: ucan: fix devres lifetime
Date: Sun, 12 Apr 2026 16:40:12 +0000 [thread overview]
Message-ID: <177601201296.3337647.8959317568301522098.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260409165942.588421-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Thu, 9 Apr 2026 18:57:07 +0200 you wrote:
> From: Johan Hovold <johan@kernel.org>
>
> USB drivers bind to USB interfaces and any device managed resources
> should have their lifetime tied to the interface rather than parent USB
> device. This avoids issues like memory leaks when drivers are unbound
> without their devices being physically disconnected (e.g. on probe
> deferral or configuration changes).
>
> [...]
Here is the summary with links:
- [net,1/2] can: ucan: fix devres lifetime
https://git.kernel.org/netdev/net/c/fed4626501c8
- [net,2/2] can: raw: fix ro->uniq use-after-free in raw_rcv()
https://git.kernel.org/netdev/net/c/a535a9217ca3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-04-12 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260409165942.588421-1-mkl@pengutronix.de>
2026-04-09 16:57 ` [PATCH net 1/2] can: ucan: fix devres lifetime Marc Kleine-Budde
2026-04-12 16:40 ` patchwork-bot+netdevbpf [this message]
2026-04-09 16:57 ` [PATCH net 2/2] can: raw: fix ro->uniq use-after-free in raw_rcv() Marc Kleine-Budde
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=177601201296.3337647.8959317568301522098.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jakob.unterwurzacher@theobroma-systems.com \
--cc=johan@kernel.org \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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