From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: 'dpdk-dev' <dev@dpdk.org>, Nipun Gupta <nipun.gupta@nxp.com>,
"Pavan Nikhilesh Bhagavatula" <pbhagavatula@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>
Subject: [dpdk-dev] [pull-request] next-eventdev 20.02 RC3 or RC4
Date: Sat, 15 Feb 2020 08:15:16 +0000 [thread overview]
Message-ID: <BYAPR18MB2424CC6DC17B04DFBAF24AEEC8140@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
The following changes since commit a0c2b3d8ee501b90eb11c2a82da0aaca19362bd3:
drivers/crypto: fix session-less mode (2020-02-13 12:41:21 +0100)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-eventdev
for you to fetch changes up to d80f21aa782a1701dd407334485c09df60f36716:
l2fwd-event: fix lcore allocation in poll mode (2020-02-15 13:37:34 +0530)
----------------------------------------------------------------
Nipun Gupta (1):
event/dpaa2: set number of order sequeuences
Pavan Nikhilesh (3):
doc: fix service core mask used in l3fwd example
app/eventdev: fix test pipeline meson build
l2fwd-event: fix lcore allocation in poll mode
Sunil Kumar Kori (1):
examples/l2fwd-event: fix return value handling from API
app/test-eventdev/meson.build | 5 ++++-
doc/guides/sample_app_ug/l3_forward.rst | 2 +-
drivers/event/dpaa2/dpaa2_eventdev.c | 2 ++
examples/l2fwd-event/l2fwd_event_generic.c | 9 +++++++--
examples/l2fwd-event/l2fwd_event_internal_port.c | 10 ++++++++--
examples/l2fwd-event/l2fwd_poll.c | 1 +
6 files changed, 23 insertions(+), 6 deletions(-)
[master]dell[dpdk-next-eventdev] $
next reply other threads:[~2020-02-15 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 8:15 Jerin Jacob Kollanukkaran [this message]
2020-02-15 13:59 ` [dpdk-dev] [pull-request] next-eventdev 20.02 RC3 or RC4 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=BYAPR18MB2424CC6DC17B04DFBAF24AEEC8140@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=nipun.gupta@nxp.com \
--cc=pbhagavatula@marvell.com \
--cc=skori@marvell.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.