From: Akhil Goyal <gakhil@marvell.com>
To: Rebecca Troy <rebecca.troy@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ciara.power@intel.com" <ciara.power@intel.com>,
Declan Doherty <declan.doherty@intel.com>,
"g.singh@nxp.com" <g.singh@nxp.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH] test/crypto: use formal array size macro
Date: Tue, 6 Jul 2021 12:18:40 +0000 [thread overview]
Message-ID: <CO6PR18MB4484D92F5A7D2FC5CC7E16BFD81B9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210705115030.520497-1-rebecca.troy@intel.com>
> Replaces the use of local ARRAY_SIZE macro, which is not used
> anywhere else, with the formal RTE_DIM macro for better
> consistency in crypto unit test.
>
> Signed-off-by: Rebecca Troy <rebecca.troy@intel.com>
> ---
Acked-by: Akhil Goyal <gakhil@marvell.com>
next prev parent reply other threads:[~2021-07-06 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 11:50 [dpdk-dev] " Rebecca Troy
2021-07-06 12:18 ` Akhil Goyal [this message]
2021-07-07 14:40 ` [dpdk-dev] [EXT] " Akhil Goyal
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=CO6PR18MB4484D92F5A7D2FC5CC7E16BFD81B9@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=rebecca.troy@intel.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).