From: Jerin Jacob <jerinjacobk@gmail.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: Nipun Gupta <nipun.gupta@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] event/dpaa: fix number of supported atomic flows
Date: Wed, 16 Oct 2019 13:28:05 +0530 [thread overview]
Message-ID: <CALBAE1Mz03Dx+puKDP==Y38CmNRSPu-b=UZexyO8Mgo-n2F-4w@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0401MB2541DDB138426F0569D206A489920@VI1PR0401MB2541.eurprd04.prod.outlook.com>
On Wed, Oct 16, 2019 at 12:11 PM Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
>
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>
Series applied to dpdk-next-eventdev/master. Thanks.
prev parent reply other threads:[~2019-10-16 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 13:47 Nipun Gupta
2019-10-11 13:47 ` [dpdk-dev] [PATCH 2/2] event/dpaa: support Tx adapter Nipun Gupta
2019-10-16 6:41 ` Hemant Agrawal
2019-10-16 6:40 ` [dpdk-dev] [PATCH 1/2] event/dpaa: fix number of supported atomic flows Hemant Agrawal
2019-10-16 7:58 ` 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='CALBAE1Mz03Dx+puKDP==Y38CmNRSPu-b=UZexyO8Mgo-n2F-4w@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=nipun.gupta@nxp.com \
--cc=stable@dpdk.org \
/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).