DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: nipun.gupta@nxp.com, dev@dpdk.org
Cc: thomas@monjalon.net, hemant.agrawal@nxp.com,
	sachin.saxena@oss.nxp.com, g.singh@nxp.com
Subject: Re: [PATCH] maintainers: update for nxp devices
Date: Fri, 3 Jun 2022 12:24:44 +0530	[thread overview]
Message-ID: <371786b5-a4ff-f6d7-d3b9-3d0dab3d89b5@oss.nxp.com> (raw)
In-Reply-To: <20220603055039.30762-1-nipun.gupta@nxp.com>

Acked-by:  Hemant Agrawal <hemant.agrawal@nxp.com>

On 6/3/2022 11:20 AM, nipun.gupta@nxp.com wrote:
> From: Nipun Gupta <nipun.gupta@nxp.com>
>
> Update and add maintainers for NXP devices and RAW device API
>
> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
> ---
>   MAINTAINERS | 14 +++++++-------
>   1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f34f6fa2e9..030100ebc7 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -515,7 +515,7 @@ F: app/test/test_event_crypto_adapter.c
>   F: doc/guides/prog_guide/event_crypto_adapter.rst
>   
>   Raw device API
> -M: Nipun Gupta <nipun.gupta@nxp.com>
> +M: Sachin Saxena <sachin.saxena@oss.nxp.com>
>   M: Hemant Agrawal <hemant.agrawal@nxp.com>
>   F: lib/rawdev/
>   F: drivers/raw/skeleton/
> @@ -1200,12 +1200,12 @@ F: doc/guides/dmadevs/cnxk.rst
>   
>   NXP DPAA DMA
>   M: Gagandeep Singh <g.singh@nxp.com>
> -M: Nipun Gupta <nipun.gupta@nxp.com>
> +M: Sachin Saxena <sachin.saxena@oss.nxp.com>
>   F: drivers/dma/dpaa/
>   F: doc/guides/dmadevs/dpaa.rst
>   
>   NXP DPAA2 QDMA
> -M: Nipun Gupta <nipun.gupta@nxp.com>
> +M: Gagandeep Singh <g.singh@nxp.com>
>   M: Hemant Agrawal <hemant.agrawal@nxp.com>
>   F: drivers/dma/dpaa2/
>   F: doc/guides/dmadevs/dpaa2.rst
> @@ -1278,13 +1278,13 @@ F: doc/guides/eventdevs/cnxk.rst
>   
>   NXP DPAA eventdev
>   M: Hemant Agrawal <hemant.agrawal@nxp.com>
> -M: Nipun Gupta <nipun.gupta@nxp.com>
> +M: Sachin Saxena <sachin.saxena@oss.nxp.com>
>   F: drivers/event/dpaa/
>   F: doc/guides/eventdevs/dpaa.rst
>   
>   NXP DPAA2 eventdev
>   M: Hemant Agrawal <hemant.agrawal@nxp.com>
> -M: Nipun Gupta <nipun.gupta@nxp.com>
> +M: Sachin Saxena <sachin.saxena@oss.nxp.com>
>   F: drivers/event/dpaa2/
>   F: doc/guides/eventdevs/dpaa2.rst
>   
> @@ -1334,7 +1334,7 @@ F: doc/guides/bbdevs/null.rst
>   F: doc/guides/bbdevs/features/null.ini
>   
>   NXP LA12xx
> -M: Nipun Gupta <nipun.gupta@nxp.com>
> +M: Gagandeep Singh <g.singh@nxp.com>
>   M: Hemant Agrawal <hemant.agrawal@nxp.com>
>   T: git://dpdk.org/next/dpdk-next-crypto
>   F: drivers/baseband/la12xx/
> @@ -1387,7 +1387,7 @@ F: examples/ntb/
>   F: doc/guides/sample_app_ug/ntb.rst
>   
>   NXP DPAA2 CMDIF
> -M: Nipun Gupta <nipun.gupta@nxp.com>
> +M: Gagandeep Singh <g.singh@nxp.com>
>   F: drivers/raw/dpaa2_cmdif/
>   F: doc/guides/rawdevs/dpaa2_cmdif.rst
>   

  reply	other threads:[~2022-06-03  6:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  5:50 nipun.gupta
2022-06-03  6:54 ` Hemant Agrawal [this message]
2022-06-07 16:50   ` 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=371786b5-a4ff-f6d7-d3b9-3d0dab3d89b5@oss.nxp.com \
    --to=hemant.agrawal@oss.nxp.com \
    --cc=dev@dpdk.org \
    --cc=g.singh@nxp.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=nipun.gupta@nxp.com \
    --cc=sachin.saxena@oss.nxp.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).