From: Akhil Goyal <akhil.goyal@nxp.com>
To: Anoob Joseph <anoobj@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: Jerin Jacob <jerinj@marvell.com>,
Narayana Prasad <pathreya@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add inline protocol in feature list
Date: Tue, 18 Feb 2020 07:40:26 +0000 [thread overview]
Message-ID: <VE1PR04MB6639204B018925FE1B39E6B3E6110@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1581953983-18994-1-git-send-email-anoobj@marvell.com>
>
> Update feature list to include inline protocol offload.
>
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> ---
> v3
> * Added inline protocol in octeontx2_vf.ini
>
> v2
> * Reworded doc following suggestions from Akhil
>
> doc/guides/nics/features.rst | 27 ++++++++++++++++++++++++++-
> doc/guides/nics/features/default.ini | 1 +
> doc/guides/nics/features/octeontx2.ini | 1 +
> doc/guides/nics/features/octeontx2_vf.ini | 1 +
> 4 files changed, 29 insertions(+), 1 deletion(-)
>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
Ferruh,
Do you want me to take this patch on crypto tree or you would be taking it.
Regards,
Akhil
next prev parent reply other threads:[~2020-02-18 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 6:53 [dpdk-dev] [PATCH] " Anoob Joseph
2020-01-21 5:40 ` Anoob Joseph
2020-01-21 16:12 ` Ferruh Yigit
2020-01-22 9:47 ` [dpdk-dev] [EXT] " Anoob Joseph
2020-02-04 14:35 ` Ferruh Yigit
2020-02-10 5:44 ` Anoob Joseph
2020-02-12 10:25 ` Akhil Goyal
2020-02-12 13:30 ` Ferruh Yigit
2020-02-12 13:48 ` Akhil Goyal
2020-02-12 13:53 ` Ferruh Yigit
2020-02-12 14:10 ` Akhil Goyal
2020-02-17 15:22 ` [dpdk-dev] [PATCH v2] " Anoob Joseph
2020-02-17 15:39 ` [dpdk-dev] [PATCH v3] " Anoob Joseph
2020-02-18 7:40 ` Akhil Goyal [this message]
2020-02-18 9:28 ` Ferruh Yigit
2020-02-18 10:02 ` Ferruh Yigit
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=VE1PR04MB6639204B018925FE1B39E6B3E6110@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=pathreya@marvell.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).