From: patchwork-bot+netdevbpf@kernel.org
To: shaozhengchao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, dsa@cumulusnetworks.com,
jiri@mellanox.com, weiyongjun1@huawei.com, yuehaibing@huawei.com
Subject: Re: [PATCH net,v3 0/2] fix some issues in netdevsim driver
Date: Thu, 27 Oct 2022 18:00:18 +0000 [thread overview]
Message-ID: <166689361881.21530.14825539415949662631.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221026014642.116261-1-shaozhengchao@huawei.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Oct 2022 09:46:40 +0800 you wrote:
> When strace tool is used to perform memory injection, memory leaks and
> files not removed issues are found. Fix them.
>
> Zhengchao Shao (2):
> netdevsim: fix memory leak in nsim_drv_probe() when
> nsim_dev_resources_register() failed
> netdevsim: remove dir in nsim_dev_debugfs_init() when creating ports
> dir failed
>
> [...]
Here is the summary with links:
- [net,v3,1/2] netdevsim: fix memory leak in nsim_drv_probe() when nsim_dev_resources_register() failed
https://git.kernel.org/netdev/net/c/6b1da9f7126f
- [net,v3,2/2] netdevsim: remove dir in nsim_dev_debugfs_init() when creating ports dir failed
https://git.kernel.org/netdev/net/c/a6aa8d0ce2cf
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-10-27 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 1:46 [PATCH net,v3 0/2] fix some issues in netdevsim driver Zhengchao Shao
2022-10-26 1:46 ` [PATCH net,v3 1/2] netdevsim: fix memory leak in nsim_drv_probe() when nsim_dev_resources_register() failed Zhengchao Shao
2022-10-27 3:36 ` Jakub Kicinski
2022-10-26 1:46 ` [PATCH net,v3 2/2] netdevsim: remove dir in nsim_dev_debugfs_init() when creating ports dir failed Zhengchao Shao
2022-10-27 18: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=166689361881.21530.14825539415949662631.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=edumazet@google.com \
--cc=jiri@mellanox.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shaozhengchao@huawei.com \
--cc=weiyongjun1@huawei.com \
--cc=yuehaibing@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 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.