From: Jerin Jacob <jerinjacobk@gmail.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>, Nipun Gupta <nipun.gupta@nxp.com>,
"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [pull-request] next-eventdev 19.11 RC1 - Iteration 2
Date: Wed, 30 Oct 2019 23:03:55 +0530 [thread overview]
Message-ID: <CALBAE1PDE55VnERnr7x3OfJP4K8yRvg4RSAZB7s=xGrjOgJa1Q@mail.gmail.com> (raw)
In-Reply-To: <BYAPR18MB2424120243A00ABDEDBE6408C86C0@BYAPR18MB2424.namprd18.prod.outlook.com>
On Fri, Oct 18, 2019 at 1:49 PM Jerin Jacob Kollanukkaran
<jerinj@marvell.com> wrote:
>
> The following changes since commit b36f587f010bba421a8fd0b4c383276ecb796ae3:
>
> rcu: fix spurious thread unregister (2019-10-18 06:13:36 +0200)
>
> are available in the Git repository at:
>
> http://dpdk.org/git/next/dpdk-next-eventdev
>
> for you to fetch changes up to 6e547f64f32ff2a3831d21931156c571e8d90f39:
>
> event/dpaa2: support Tx adapter (2019-10-18 13:33:09 +0530)
>
> ----------------------------------------------------------------
>
> Changes pushed to post RC1.
>
> 1) Crypto adapter fixes
> http://patches.dpdk.org/project/dpdk/list/?series=6648&state=*
Hemant,
I am planning to give a pull request by 5th Nov. If it needs to be
part of RC2. Please complete the change request and review before it.
prev parent reply other threads:[~2019-10-30 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 8:19 Jerin Jacob Kollanukkaran
2019-10-23 14:22 ` Thomas Monjalon
2019-10-30 17:33 ` Jerin Jacob [this message]
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='CALBAE1PDE55VnERnr7x3OfJP4K8yRvg4RSAZB7s=xGrjOgJa1Q@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=nipun.gupta@nxp.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 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).