From: Thomas Monjalon <thomas@monjalon.net>
To: Nicolas Chautru <nicolas.chautru@intel.com>
Cc: dev@dpdk.org, gakhil@marvell.com, trix@redhat.com,
hemant.agrawal@nxp.com, mingshan.zhang@intel.com,
david.marchand@redhat.com,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: Re: [PATCH v2] maintainers: add explicit maintainer for some bbdev PMDs
Date: Fri, 18 Mar 2022 21:29:39 +0100 [thread overview]
Message-ID: <2624076.mvXUDI8C0e@thomas> (raw)
In-Reply-To: <1647553553-36995-2-git-send-email-nicolas.chautru@intel.com>
17/03/2022 22:45, Nicolas Chautru:
> +Intel PMDs
It's not all Intel PMDs, just Intel baseband drivers.
> +M: Nicolas Chautru <nicolas.chautru@intel.com>
> +T: git://dpdk.org/next/dpdk-next-crypto
> +F: drivers/baseband/turbo_sw/
> +F: drivers/baseband/fpga_lte_fec/
> +F: drivers/baseband/fpga_5gnr_fec/
> +F: drivers/baseband/acc100/
> +F: doc/guides/bbdevs/turbo_sw.rst
> +F: doc/guides/bbdevs/fpga_lte_fec.rst
> +F: doc/guides/bbdevs/fpga_5gnr_fec.rst
> +F: doc/guides/bbdevs/acc100.rst
> +F: doc/guides/bbdevs/features/turbo_sw.ini
> +F: doc/guides/bbdevs/features/fpga_lte_fec.ini
> +F: doc/guides/bbdevs/features/fpga_5gnr_fec.ini
> +F: doc/guides/bbdevs/features/acc100.ini
It's better to group lines per driver.
next prev parent reply other threads:[~2022-03-18 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 21:45 [PATCH v2] maintainers: add explicit maintainer for some bbdev PMDs Nicolas Chautru
2022-03-17 21:45 ` Nicolas Chautru
2022-03-18 20:29 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-17 22:47 Nicolas Chautru
2022-03-17 22:47 ` Nicolas Chautru
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=2624076.mvXUDI8C0e@thomas \
--to=thomas@monjalon.net \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=mingshan.zhang@intel.com \
--cc=nicolas.chautru@intel.com \
--cc=trix@redhat.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.