From: Jinjie Ruan <ruanjinjie@huawei.com>
To: <lars.povlsen@microchip.com>, <Steen.Hegelund@microchip.com>,
<daniel.machon@microchip.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>
Cc: <ruanjinjie@huawei.com>
Subject: [PATCH net 0/5] net: microchip: sparx5: Fix some memory leaks in vcap_api_kunit
Date: Fri, 8 Sep 2023 12:00:06 +0800 [thread overview]
Message-ID: <20230908040011.2620468-1-ruanjinjie@huawei.com> (raw)
There are some memory leaks in vcap_api_kunit, this patchset fixes them.
Jinjie Ruan (5):
net: microchip: sparx5: Fix memory leak for
vcap_api_rule_add_keyvalue_test()
net: microchip: sparx5: Fix memory leak for
vcap_api_rule_add_actionvalue_test()
net: microchip: sparx5: Fix possible memory leak in
vcap_api_encode_rule_test()
net: microchip: sparx5: Fix possible memory leaks in
test_vcap_xn_rule_creator()
net: microchip: sparx5: Fix possible memory leaks in vcap_api_kunit
.../ethernet/microchip/vcap/vcap_api_kunit.c | 58 +++++++++++++++++--
1 file changed, 53 insertions(+), 5 deletions(-)
--
2.34.1
next reply other threads:[~2023-09-08 4:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 4:00 Jinjie Ruan [this message]
2023-09-08 4:00 ` [PATCH net 1/5] net: microchip: sparx5: Fix memory leak for vcap_api_rule_add_keyvalue_test() Jinjie Ruan
2023-09-08 4:00 ` [PATCH net 2/5] net: microchip: sparx5: Fix memory leak for vcap_api_rule_add_actionvalue_test() Jinjie Ruan
2023-09-08 11:29 ` Daniel Machon
2023-09-08 4:00 ` [PATCH net 3/5] net: microchip: sparx5: Fix possible memory leak in vcap_api_encode_rule_test() Jinjie Ruan
2023-09-08 4:00 ` [PATCH net 4/5] net: microchip: sparx5: Fix possible memory leaks in test_vcap_xn_rule_creator() Jinjie Ruan
2023-09-08 7:32 ` kernel test robot
2023-09-09 2:06 ` kernel test robot
2023-09-08 4:00 ` [PATCH net 5/5] net: microchip: sparx5: Fix possible memory leaks in vcap_api_kunit Jinjie Ruan
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=20230908040011.2620468-1-ruanjinjie@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=Steen.Hegelund@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).