From: patchwork-bot+netdevbpf@kernel.org
To: Shang XiaoJing <shangxiaojing@huawei.com>
Cc: krzysztof.kozlowski@linaro.org, pavel@denx.de,
u.kleine-koenig@pengutronix.de, kuba@kernel.org,
michael@walle.cc, cuissard@marvell.com, sameo@linux.intel.com,
clement.perrochaud@nxp.com, r.baldyga@samsung.com,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] nfc: Fix potential memory leak of skb
Date: Mon, 21 Nov 2022 09:00:16 +0000 [thread overview]
Message-ID: <166902121615.26857.6390374258212309010.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221117113714.12776-1-shangxiaojing@huawei.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 17 Nov 2022 19:37:11 +0800 you wrote:
> There are still somewhere maybe leak the skb, fix the memleaks by adding
> fail path.
>
> Shang XiaoJing (3):
> nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send()
> nfc: nxp-nci: Fix potential memory leak in nxp_nci_send()
> nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send()
>
> [...]
Here is the summary with links:
- [1/3] nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send()
https://git.kernel.org/netdev/net/c/e204ead35401
- [2/3] nfc: nxp-nci: Fix potential memory leak in nxp_nci_send()
https://git.kernel.org/netdev/net/c/614761e1119c
- [3/3] nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send()
https://git.kernel.org/netdev/net/c/60dcb5ff55e5
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-11-21 9:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 11:37 [PATCH 0/3] nfc: Fix potential memory leak of skb Shang XiaoJing
2022-11-17 11:37 ` [PATCH 1/3] nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() Shang XiaoJing
2022-11-17 11:37 ` [PATCH 2/3] nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() Shang XiaoJing
2022-11-17 11:37 ` [PATCH 3/3] nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() Shang XiaoJing
2022-11-21 9:00 ` patchwork-bot+netdevbpf [this message]
2022-11-23 19:04 ` [PATCH 0/3] nfc: Fix potential memory leak of skb Pavel Machek
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=166902121615.26857.6390374258212309010.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=clement.perrochaud@nxp.com \
--cc=cuissard@marvell.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=pavel@denx.de \
--cc=r.baldyga@samsung.com \
--cc=sameo@linux.intel.com \
--cc=shangxiaojing@huawei.com \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).