From: "Min Hu (Connor)" <humin29@huawei.com>
To: <dev@dpdk.org>
Cc: <ferruh.yigit@intel.com>, <jerinj@marvell.com>
Subject: [dpdk-dev] [PATCH 0/2] bugfix for lib eventdev
Date: Fri, 30 Apr 2021 17:34:36 +0800 [thread overview]
Message-ID: <1619775278-25857-1-git-send-email-humin29@huawei.com> (raw)
This patch set contains two bugfixes for lib eventdev.
Chengwen Feng (2):
eventdev: remove redundant setting thread name
eventdev: fix memory leakage when create thread fail
lib/eventdev/rte_event_eth_rx_adapter.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
2.7.4
next reply other threads:[~2021-04-30 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 9:34 Min Hu (Connor) [this message]
2021-04-30 9:34 ` [dpdk-dev] [PATCH 1/2] eventdev: remove redundant setting thread name Min Hu (Connor)
2021-05-01 12:38 ` Jerin Jacob
2021-04-30 9:34 ` [dpdk-dev] [PATCH 2/2] eventdev: fix memory leakage when create thread fail Min Hu (Connor)
2021-05-01 12:38 ` Jerin Jacob
2021-05-01 14:41 ` Jerin Jacob
2021-04-30 15:35 ` [dpdk-dev] [EXT] [PATCH 0/2] bugfix for lib eventdev Pavan Nikhilesh Bhagavatula
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=1619775278-25857-1-git-send-email-humin29@huawei.com \
--to=humin29@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.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).