From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-eventdev 17.08 rc2
Date: Thu, 20 Jul 2017 09:52:11 +0530 [thread overview]
Message-ID: <20170720042203.GA19912@jerin> (raw)
The following changes since commit da94a999d3eae6a4c565f2a23c3ab303909e9b53:
examples/vhost_scsi: introduce a new sample app (2017-07-19 22:49:47 +0300)
are available in the git repository at:
http://dpdk.org/git/next/dpdk-next-eventdev
for you to fetch changes up to cb78ef9859ff68b9e260a844f151055ebd9ae78f:
eventdev: fix memory realloc check in port config (2017-07-20 09:49:47 +0530)
----------------------------------------------------------------
Harry van Haaren (1):
eventdev: fix memory realloc check in port config
Nipun Gupta (1):
event/dpaa2: advertise the burst mode capability
drivers/event/dpaa2/dpaa2_eventdev.c | 3 ++-
lib/librte_eventdev/rte_eventdev.c | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
next reply other threads:[~2017-07-20 4:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 4:22 Jerin Jacob [this message]
2017-07-20 6:25 ` 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=20170720042203.GA19912@jerin \
--to=jerin.jacob@caviumnetworks.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).