From: "Dooley, Brian" <brian.dooley@intel.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "jerinj@marvell.com" <jerinj@marvell.com>,
"anoobj@marvell.com" <anoobj@marvell.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: RE: [PATCH] maintainers: update for FIPS validation
Date: Thu, 30 Mar 2023 09:07:39 +0000 [thread overview]
Message-ID: <SJ0PR11MB50565AB89494174C4ADEE0AD838E9@SJ0PR11MB5056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230329110106.465791-1-gmuthukrishn@marvell.com>
Hi Gowrishankar,
> -----Original Message-----
> From: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> Sent: Wednesday 29 March 2023 12:01
> To: dev@dpdk.org
> Cc: jerinj@marvell.com; anoobj@marvell.com; Akhil Goyal
> <gakhil@marvell.com>; Dooley, Brian <brian.dooley@intel.com>;
> Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> Subject: [PATCH] maintainers: update for FIPS validation
>
> Add co-maintainer for FIPS validation example.
>
> Signed-off-by: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 280058adfc..8df23e5099 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1809,6 +1809,7 @@ F: doc/guides/sample_app_ug/ethtool.rst
>
> FIPS validation example
> M: Brian Dooley <brian.dooley@intel.com>
> +M: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
> F: examples/fips_validation/
> F: doc/guides/sample_app_ug/fips_validation.rst
>
> --
> 2.25.1
Acked-by: Brian Dooley <brian.dooley@intel.com>
next prev parent reply other threads:[~2023-03-30 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 11:01 Gowrishankar Muthukrishnan
2023-03-29 11:26 ` Akhil Goyal
2023-03-30 9:07 ` Dooley, Brian [this message]
2023-03-31 9:24 ` 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=SJ0PR11MB50565AB89494174C4ADEE0AD838E9@SJ0PR11MB5056.namprd11.prod.outlook.com \
--to=brian.dooley@intel.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=gmuthukrishn@marvell.com \
--cc=jerinj@marvell.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).