From: Akhil Goyal <akhil.goyal@nxp.com>
To: Vikas Gupta <vikas.gupta@broadcom.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "vikram.prakash@broadcom.com" <vikram.prakash@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH v1 1/1] crypto/bcmfs: update documentation file
Date: Wed, 28 Oct 2020 12:22:29 +0000 [thread overview]
Message-ID: <AM5PR04MB315331922A457336FA6FEA10E6170@AM5PR04MB3153.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201027052922.7606-2-vikas.gupta@broadcom.com>
> Subject: [PATCH v1 1/1] crypto/bcmfs: update documentation file
>
> Update bcmfs.rst file with supported features and devices.
>
Title updated " doc: update bcmfs crypto PMD features"
> Signed-off-by: Vikas Gupta <vikas.gupta@broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Reviewed-by: JP Lee <jongpil.lee@broadcom.com>
> ---
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2020-10-28 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 5:29 [dpdk-dev] [PATCH v1 0/1] " Vikas Gupta
2020-10-27 5:29 ` [dpdk-dev] [PATCH v1 1/1] crypto/bcmfs: " Vikas Gupta
2020-10-28 12:22 ` Akhil Goyal [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=AM5PR04MB315331922A457336FA6FEA10E6170@AM5PR04MB3153.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=vikas.gupta@broadcom.com \
--cc=vikram.prakash@broadcom.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).