From: patchwork-bot+netdevbpf@kernel.org
To: Ziyang Xuan <william.xuanziyang@huawei.com>
Cc: krzysztof.kozlowski@canonical.com, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] fix two possible memory leak problems in NFC digital module
Date: Thu, 14 Oct 2021 00:50:06 +0000 [thread overview]
Message-ID: <163417260699.14585.6395298132733213197.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1634111083.git.william.xuanziyang@huawei.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 13 Oct 2021 15:49:53 +0800 you wrote:
> Fix two possible memory leak problems in NFC digital module.
>
> Ziyang Xuan (2):
> NFC: digital: fix possible memory leak in digital_tg_listen_mdaa()
> NFC: digital: fix possible memory leak in digital_in_send_sdd_req()
>
> net/nfc/digital_core.c | 9 +++++++--
> net/nfc/digital_technology.c | 8 ++++++--
> 2 files changed, 13 insertions(+), 4 deletions(-)
Here is the summary with links:
- [net,1/2] NFC: digital: fix possible memory leak in digital_tg_listen_mdaa()
https://git.kernel.org/netdev/net/c/58e7dcc9ca29
- [net,2/2] NFC: digital: fix possible memory leak in digital_in_send_sdd_req()
https://git.kernel.org/netdev/net/c/291c932fc369
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:[~2021-10-14 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 7:49 [PATCH net 0/2] fix two possible memory leak problems in NFC digital module Ziyang Xuan
2021-10-13 7:50 ` [PATCH net 1/2] NFC: digital: fix possible memory leak in digital_tg_listen_mdaa() Ziyang Xuan
2021-10-13 9:35 ` Krzysztof Kozlowski
2021-10-13 7:50 ` [PATCH net 2/2] NFC: digital: fix possible memory leak in digital_in_send_sdd_req() Ziyang Xuan
2021-10-13 9:36 ` Krzysztof Kozlowski
2021-10-14 0: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=163417260699.14585.6395298132733213197.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=krzysztof.kozlowski@canonical.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=william.xuanziyang@huawei.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;
as well as URLs for NNTP newsgroup(s).