From: patchwork-bot+netdevbpf@kernel.org
To: Yan Cangang <nalanzeyu@gmail.com>
Cc: leon@kernel.org, kuba@kernel.org, Mark-MC.Lee@mediatek.com,
john@phrozen.org, nbd@nbd.name, sean.wang@mediatek.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] net: ethernet: mtk_eth_soc: fix memory leak in error path
Date: Wed, 23 Nov 2022 05:00:19 +0000 [thread overview]
Message-ID: <166917961980.4515.18210373992348311213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221120055259.224555-1-nalanzeyu@gmail.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 20 Nov 2022 13:52:57 +0800 you wrote:
> v1: https://lore.kernel.org/netdev/20221112233239.824389-1-nalanzeyu@gmail.com/T/
> v2:
> - clean up commit message
> - new mtk_ppe_deinit() function, call it before calling mtk_mdio_cleanup()
> v3:
> - split into two patches
>
> [...]
Here is the summary with links:
- [net,v3,1/2] net: ethernet: mtk_eth_soc: fix resource leak in error path
https://git.kernel.org/netdev/net/c/8110437e5961
- [net,v3,2/2] net: ethernet: mtk_eth_soc: fix memory leak in error path
https://git.kernel.org/netdev/net/c/603ea5e7ffa7
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:[~2022-11-23 5:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 5:52 [PATCH net v3 0/2] net: ethernet: mtk_eth_soc: fix memory leak in error path Yan Cangang
2022-11-20 5:52 ` [PATCH net v3 1/2] net: ethernet: mtk_eth_soc: fix resource " Yan Cangang
2022-11-20 5:52 ` [PATCH net v3 2/2] net: ethernet: mtk_eth_soc: fix memory " Yan Cangang
2022-11-22 12:46 ` [PATCH net v3 0/2] " Leon Romanovsky
2022-11-23 5:00 ` 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=166917961980.4515.18210373992348311213.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Mark-MC.Lee@mediatek.com \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=nalanzeyu@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=sean.wang@mediatek.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).