From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Nipun Gupta <nipun.gupta@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "jerinj@marvell.com" <jerinj@marvell.com>,
Nipun Gupta <nipun.gupta@nxp.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] event/dpaa: support Tx adapter
Date: Wed, 16 Oct 2019 06:41:31 +0000 [thread overview]
Message-ID: <VI1PR0401MB254115E7933DF7A16D0C7C7089920@VI1PR0401MB2541.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20191011134757.3359-2-nipun.gupta@nxp.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
next prev parent reply other threads:[~2019-10-16 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 13:47 [dpdk-dev] [PATCH 1/2] event/dpaa: fix number of supported atomic flows 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 [this message]
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
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=VI1PR0401MB254115E7933DF7A16D0C7C7089920@VI1PR0401MB2541.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=nipun.gupta@nxp.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 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).