From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [pull-request] next-eventdev 21.02-rc3
Date: Thu, 4 Feb 2021 18:22:23 +0000 [thread overview]
Message-ID: <BYAPR18MB2424E9DEA5EEFE06358CD3F5C8B39@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
The following changes since commit f6f2d22401531ba06f5a1c967853453b0cbb8a9d:
devtools: fix examples build test (2021-02-02 23:58:22 +0100)
are available in the Git repository at:
http://dpdk.org/git/next/dpdk-next-eventdev
for you to fetch changes up to b982f0ef3f58e8381fa473c2636ea4725b505f5a:
eventdev: remove return value comment in PMD API (2021-02-04 18:21:45 +0530)
----------------------------------------------------------------
Harry van Haaren (1):
eventdev: remove return value comment in PMD API
Timothy McDaniel (1):
event/dlb: fix accessing uninitialized variables
drivers/event/dlb/dlb.c | 6 +++---
lib/librte_eventdev/eventdev_pmd.h | 3 ---
2 files changed, 3 insertions(+), 6 deletions(-)
reply other threads:[~2021-02-04 18:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BYAPR18MB2424E9DEA5EEFE06358CD3F5C8B39@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).