From: Akhil Goyal <gakhil@marvell.com>
To: Dharmik Thakkar <dharmikjayesh.thakkar@arm.com>,
Thomas Monjalon <thomas@monjalon.net>, Kai Ji <kai.ji@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "nd@arm.com" <nd@arm.com>,
Ruifeng Wang <ruifeng.wang@arm.com>
Subject: RE: [EXT] [PATCH v3] doc: update QAT cryptodev guide to run on aarch64
Date: Fri, 27 Oct 2023 19:16:37 +0000 [thread overview]
Message-ID: <CO6PR18MB448453AD8FC8ED9831805539D8DCA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230809153814.506988-1-dharmikjayesh.thakkar@arm.com>
> Update guide with instructions to run on Aarch64 based Ampere Altra
> platform
>
> Signed-off-by: Dharmik Thakkar <dharmikjayesh.thakkar@arm.com>
> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com>
> ---
> v3:
> - Fix duplicate target warning by using anonymous reference
> v2:
> - Update driver guide with instructions to run on aarch64 instead
> ---
> .mailmap | 2 +-
> doc/guides/cryptodevs/qat.rst | 6 ++++++
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/.mailmap b/.mailmap
> index 864d33ee46fb..bb79fd4673ef 100644
> --- a/.mailmap
> +++ b/.mailmap
> @@ -319,7 +319,7 @@ Devendra Singh Rawat <dsinghrawat@marvell.com>
> Dex Chen <dex.chen@ruckuswireless.com>
> Dexia Li <dexia.li@jaguarmicro.com>
> Dexuan Cui <decui@microsoft.com>
> -Dharmik Thakkar <dharmik.thakkar@arm.com>
> +Dharmik Thakkar <dharmikjayesh.thakkar@arm.com>
Change in email ID should be added and not replaced.
Updated .mailmap to have both the email IDs.
Applied to dpdk-next-crypto
prev parent reply other threads:[~2023-10-27 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 22:37 [PATCH] doc: announce QAT support " Dharmik Thakkar
2023-07-27 21:13 ` Thomas Monjalon
2023-08-08 14:52 ` [PATCH v2] doc: update QAT cryptodev guide to run " Dharmik Thakkar
2023-08-09 15:38 ` [PATCH v3] " Dharmik Thakkar
2023-10-27 19:16 ` 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=CO6PR18MB448453AD8FC8ED9831805539D8DCA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=dharmikjayesh.thakkar@arm.com \
--cc=kai.ji@intel.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.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).