From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
Gavin Hu <gavin.hu@arm.com>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] MAINTAINERS: update armv8 crypto PMD maintainership
Date: Wed, 27 Nov 2019 17:33:31 +0900 [thread overview]
Message-ID: <CALBAE1OSuB5vvDpOquaMcSUZr1TPJR4YGjHiYL2fLw9ur99GXA@mail.gmail.com> (raw)
In-Reply-To: <20191127081454.174465-1-ruifeng.wang@arm.com>
On Wed, Nov 27, 2019 at 5:15 PM Ruifeng Wang <ruifeng.wang@arm.com> wrote:
>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
> ---
Request to add some git comments while merging or sending the v2.
Something like below,
It is expected to update this PMD to be in line with ARM's crypto library.
Update the maintainership to refect the change.
Acked-by: Jerin Jacob <jerinj@marvell.com>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4a0c9a47e..5f7213872 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -940,7 +940,7 @@ F: doc/guides/cryptodevs/ccp.rst
> F: doc/guides/cryptodevs/features/ccp.ini
>
> ARMv8 Crypto
> -M: Jerin Jacob <jerinj@marvell.com>
> +M: Ruifeng Wang <ruifeng.wang@arm.com>
> F: drivers/crypto/armv8/
> F: doc/guides/cryptodevs/armv8.rst
> F: doc/guides/cryptodevs/features/armv8.ini
> --
> 2.17.1
>
next prev parent reply other threads:[~2019-11-27 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 8:14 Ruifeng Wang
2019-11-27 8:33 ` Jerin Jacob [this message]
2019-11-27 8:49 ` Ruifeng Wang (Arm Technology China)
2019-11-27 8:47 ` [dpdk-dev] [PATCH v2] " Ruifeng Wang
2019-11-27 23:49 ` Thomas Monjalon
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=CALBAE1OSuB5vvDpOquaMcSUZr1TPJR4YGjHiYL2fLw9ur99GXA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.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).