From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"timothy.mcdaniel@intel.com" <timothy.mcdaniel@intel.com>
Subject: [dpdk-dev] [pull-request] next-eventdev 20.11 RC4
Date: Fri, 13 Nov 2020 10:00:24 +0000 [thread overview]
Message-ID: <BYAPR18MB2424590204FEFFC812D04F7DC8E60@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
The following changes since commit 4630290af46ed44a58515067b6d2add9c044252a:
mbuf: move pool pointer in first half (2020-11-12 16:39:10 +0100)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-eventdev
for you to fetch changes up to c919c1039c07408da9b4ea0fd341818dffed94f7:
app/eventdev: fix segfault with incorrect timer adadpters (2020-11-13 14:22:11 +0530)
----------------------------------------------------------------
Pavan Nikhilesh (1):
app/eventdev: fix segfault with incorrect timer adadpters
Timothy McDaniel (8):
event/dlb: fix memory overrun Coverity warning
event/dlb: fix no-effect Coverity warning
event/dlb2: fix dereference null pointer Coverity warning
event/dlb2: add missing sections to documentation
event/dlb2: add missing delayed token pop logic
event/dlb2: remove duplicate/unused PCI code and constants
event/dlb: do not free memzone if port create succeeds
event/dlb: remove duplicate/unused PCI code and constants
app/test-eventdev/evt_options.c | 4 +
doc/guides/eventdevs/dlb2.rst | 47 ++++++
drivers/event/dlb/dlb.c | 1 -
drivers/event/dlb/pf/dlb_main.c | 54 ++-----
drivers/event/dlb/pf/dlb_pf.c | 2 +
drivers/event/dlb2/dlb2.c | 314 +++++++++++++++++++++++--------------
drivers/event/dlb2/dlb2_selftest.c | 11 +-
drivers/event/dlb2/pf/dlb2_main.c | 46 +-----
8 files changed, 277 insertions(+), 202 deletions(-)
next reply other threads:[~2020-11-13 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 10:00 Jerin Jacob Kollanukkaran [this message]
2020-11-15 14:01 ` Thomas Monjalon
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=BYAPR18MB2424590204FEFFC812D04F7DC8E60@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--cc=timothy.mcdaniel@intel.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).