From: patchwork-bot+netdevbpf@kernel.org
To: Xiaohui Zhang <xiaohuizhang@ruc.edu.cn>
Cc: krzysztof.kozlowski@linaro.org, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] nfc: nfcmrvl: Fix memory leak in nfcmrvl_play_deferred
Date: Wed, 08 Jun 2022 18:00:15 +0000 [thread overview]
Message-ID: <165471121506.25792.17494847450565348748.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220607083230.6182-1-xiaohuizhang@ruc.edu.cn>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Jun 2022 16:32:30 +0800 you wrote:
> Similar to the handling of play_deferred in commit 19cfe912c37b
> ("Bluetooth: btusb: Fix memory leak in play_deferred"), we thought
> a patch might be needed here as well.
>
> Currently usb_submit_urb is called directly to submit deferred tx
> urbs after unanchor them.
>
> [...]
Here is the summary with links:
- [1/1] nfc: nfcmrvl: Fix memory leak in nfcmrvl_play_deferred
https://git.kernel.org/netdev/net/c/8a4d480702b7
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:[~2022-06-08 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 8:32 [PATCH 1/1] nfc: nfcmrvl: Fix memory leak in nfcmrvl_play_deferred Xiaohui Zhang
2022-06-07 12:44 ` Krzysztof Kozlowski
2022-06-08 18:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-05 8:14 Xiaohui Zhang
2022-06-06 10:46 ` Krzysztof Kozlowski
2022-06-03 16:31 Xiaohui Zhang
2022-06-04 1:33 ` Jakub Kicinski
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=165471121506.25792.17494847450565348748.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiaohuizhang@ruc.edu.cn \
/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.