From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dpdk-dev <dev@dpdk.org>
Subject: [dpdk-dev] [pull-request] next-eventdev 20.08 RC3
Date: Fri, 24 Jul 2020 05:27:23 +0000 [thread overview]
Message-ID: <BYAPR18MB24248509DA4C294D109E1DD1C8770@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
The following changes since commit 3a66b2f90bcb08347626e26f206df07ebfa40058:
doc: announce removal of mbuf legacy refcnt field (2020-07-21 10:30:35 +0200)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-eventdev
for you to fetch changes up to 30ab5afc2e0498d06dffdc6109a42a8e4ab8bb07:
event/dpaa2: add all type queue capability flag (2020-07-24 10:52:41 +0530)
----------------------------------------------------------------
Apeksha Gupta (2):
app/test-eventdev: fix capability check in pipeline ATQ test
event/dpaa2: add all type queue capability flag
Yunjian Wang (1):
event/dpaa: remove dead code
app/test-eventdev/test_pipeline_atq.c | 2 ++
drivers/event/dpaa/dpaa_eventdev.c | 4 +---
drivers/event/dpaa2/dpaa2_eventdev.c | 3 ++-
3 files changed, 5 insertions(+), 4 deletions(-)
next reply other threads:[~2020-07-24 5:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 5:27 Jerin Jacob Kollanukkaran [this message]
2020-07-28 22:10 ` 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=BYAPR18MB24248509DA4C294D109E1DD1C8770@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).