From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
'Nipun Gupta' <nipun.gupta@nxp.com>,
"gage.eads@intel.com" <gage.eads@intel.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>,
Nikhil Rao <nikhil.rao@intel.com>,
"harry.van.haaren@intel.com" <harry.van.haaren@intel.com>
Subject: Re: [dpdk-dev] [pull-request] next-eventdev 19.11 PRE-RC1
Date: Tue, 15 Oct 2019 21:06:55 +0200 [thread overview]
Message-ID: <1855795.oHiGt4ib2l@xps> (raw)
In-Reply-To: <BYAPR18MB24246B36C93061D326259949C8990@BYAPR18MB2424.namprd18.prod.outlook.com>
05/10/2019 15:50, Jerin Jacob Kollanukkaran:
> http://dpdk.org/git/next/dpdk-next-eventdev
Was pulled on last Saturday.
> Note:
> - I will be on vacation next week.
> - Following are the pending patches in Eventdev tree for 19.11. Based on the review comments and time the review completes, We can merge in post RC1 or in RC1.
>
> a) Tx adapter API change
> http://patches.dpdk.org/patch/60528/
This change should not be post -rc1.
Please make sure to merge it soon.
> b) NXP Tx adapter implementation
> http://patches.dpdk.org/user/todo/dpdk/?series=6696
> c) Crypto adapter changes
> http://patches.dpdk.org/user/todo/dpdk/?series=6648
> d) l2fwd-event(Waiting for NXP Ack)
> http://patches.dpdk.org/project/dpdk/list/?series=6676
next prev parent reply other threads:[~2019-10-15 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 13:50 [dpdk-dev] [pull-request] next-eventdev 19.11 PRE-RC1 Jerin Jacob Kollanukkaran
2019-10-15 19:06 ` Thomas Monjalon [this message]
2019-10-16 12:14 ` Jerin Jacob
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=1855795.oHiGt4ib2l@xps \
--to=thomas@monjalon.net \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=nikhil.rao@intel.com \
--cc=nipun.gupta@nxp.com \
--cc=pbhagavatula@marvell.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 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.