All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Nicolas Chautru <nicolas.chautru@intel.com>
Cc: dev@dpdk.org, gakhil@marvell.com, bruce.richardson@intel.com
Subject: Re: [PATCH v1] maintainers: add explicit maintainer for some bbdev PMDs
Date: Wed, 09 Mar 2022 00:23:07 +0100	[thread overview]
Message-ID: <5072825.0vhOF50zNu@thomas> (raw)
In-Reply-To: <1646333498-18883-2-git-send-email-nicolas.chautru@intel.com>

03/03/2022 19:51, Nicolas Chautru:
> These were implicit from DPDK script but adding
> separate reference to make it explicit
> 
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
>  MAINTAINERS | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7577834..004ec91 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -421,6 +421,10 @@ T: git://dpdk.org/next/dpdk-next-crypto
>  F: lib/bbdev/
>  F: doc/guides/prog_guide/bbdev.rst
>  F: drivers/baseband/

I think you can remove the above catch-all.

> +F: drivers/baseband/turbo_sw/
> +F: drivers/baseband/fpga_lte_fec/
> +F: drivers/baseband/fpga_5gnr_fec/
> +F: drivers/baseband/acc100/

I would prefer a separate section for Intel baseband drivers.

>  F: doc/guides/bbdevs/
>  F: app/test-bbdev/
>  F: doc/guides/tools/testbbdev.rst





  parent reply	other threads:[~2022-03-08 23:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 18:51 [PATCH v1] maintainers: add explicit maintainer for some bbdev PMDs Nicolas Chautru
2022-03-03 18:51 ` Nicolas Chautru
2022-03-04  8:57   ` Bruce Richardson
2022-03-08 23:23   ` Thomas Monjalon [this message]
2022-03-09  8:44     ` David Marchand

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=5072825.0vhOF50zNu@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=nicolas.chautru@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.