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>,
Shijith Thotton <sthotton@marvell.com>,
"Pavan Nikhilesh Bhagavatula" <pbhagavatula@marvell.com>
Subject: [dpdk-dev] [pull-request] next-eventdev 20.11 rc5
Date: Fri, 20 Nov 2020 12:30:00 +0000 [thread overview]
Message-ID: <BYAPR18MB24245A22577F0D5323BCF7EBC8FF0@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
The following changes since commit 2069f9eefca06190377bbff14734e2326439df42:
version: 20.11-rc4 (2020-11-16 00:14:43 +0100)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-eventdev
for you to fetch changes up to 08c8e18b9cf78472dd0bcfdf484f0ff27b541020:
event/octeontx2: unlink queues during port release (2020-11-20 23:23:47 +0530)
----------------------------------------------------------------
Pavan Nikhilesh (3):
event/octeontx2: remove selftest from dev args
event/octeontx: remove selftest from dev args
event/octeontx2: fix unconditional Tx flush
Shijith Thotton (1):
event/octeontx2: unlink queues during port release
Timothy McDaniel (1):
event/dlb: fix potential null dereference
doc/guides/eventdevs/octeontx.rst | 12 ----
doc/guides/eventdevs/octeontx2.rst | 9 ---
drivers/event/dlb/dlb_selftest.c | 7 +-
drivers/event/octeontx/ssovf_evdev.c | 22 ++----
drivers/event/octeontx/ssovf_evdev.h | 2 -
drivers/event/octeontx2/otx2_evdev.c | 108 ++++++++++++++++-------------
drivers/event/octeontx2/otx2_evdev.h | 14 +++-
drivers/event/octeontx2/otx2_evdev_adptr.c | 24 +++++--
drivers/event/octeontx2/otx2_worker.c | 14 ++--
drivers/event/octeontx2/otx2_worker.h | 20 ++++--
10 files changed, 124 insertions(+), 108 deletions(-)
~
next reply other threads:[~2020-11-20 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 12:30 Jerin Jacob Kollanukkaran [this message]
2020-11-21 13:24 ` 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=BYAPR18MB24245A22577F0D5323BCF7EBC8FF0@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=pbhagavatula@marvell.com \
--cc=sthotton@marvell.com \
--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).