From: "Zhang, Fan" <fanzhang.oss@gmail.com>
To: dev@dpdk.org
Subject: Re: [PATCH] maintainers: split baseband from crypto tree
Date: Mon, 5 Dec 2022 10:58:23 +0000 [thread overview]
Message-ID: <b14d05a6-a5c1-c312-8ac2-b53d6da4259b@gmail.com> (raw)
In-Reply-To: <20221205075944.822372-1-gakhil@marvell.com>
On 12/5/2022 7:59 AM, Akhil Goyal wrote:
> Baseband patches are now split from dpdk-next-crypto,
> All baseband patches need to be submitted to dpdk-next-baseband
> which will be maintained by Maxime.
>
> Cc: maxime.coquelin@redhat.com
>
> Signed-off-by: Akhil Goyal <gakhil@marvell.com>
> ---
> MAINTAINERS | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 22ef2ea4b9..3dc3f5b348 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -61,6 +61,10 @@ Next-eventdev Tree
> M: Jerin Jacob <jerinj@marvell.com>
> T: git://dpdk.org/next/dpdk-next-eventdev
>
> +Next-baseband Tree
> +M: Maxime Coquelin <maxime.coquelin@redhat.com>
> +T: git://dpdk.org/next/dpdk-next-baseband
> +
> Stable Branches
> M: Luca Boccassi <bluca@debian.org>
> M: Kevin Traynor <ktraynor@redhat.com>
> @@ -432,7 +436,7 @@ F: app/test-pmd/cmdline_mtr.*
>
> Baseband API
> M: Nicolas Chautru <nicolas.chautru@intel.com>
> -T: git://dpdk.org/next/dpdk-next-crypto
> +T: git://dpdk.org/next/dpdk-next-baseband
> F: lib/bbdev/
> F: doc/guides/prog_guide/bbdev.rst
> F: doc/guides/bbdevs/features/default.ini
> @@ -1346,7 +1350,7 @@ Baseband Drivers
>
> Intel baseband
> M: Nicolas Chautru <nicolas.chautru@intel.com>
> -T: git://dpdk.org/next/dpdk-next-crypto
> +T: git://dpdk.org/next/dpdk-next-baseband
> F: drivers/baseband/turbo_sw/
> F: doc/guides/bbdevs/turbo_sw.rst
> F: doc/guides/bbdevs/features/turbo_sw.ini
> @@ -1365,7 +1369,7 @@ F: doc/guides/bbdevs/features/acc200.ini
>
> Null baseband
> M: Nicolas Chautru <nicolas.chautru@intel.com>
> -T: git://dpdk.org/next/dpdk-next-crypto
> +T: git://dpdk.org/next/dpdk-next-baseband
> F: drivers/baseband/null/
> F: doc/guides/bbdevs/null.rst
> F: doc/guides/bbdevs/features/null.ini
> @@ -1373,7 +1377,7 @@ F: doc/guides/bbdevs/features/null.ini
> NXP LA12xx
> M: Gagandeep Singh <g.singh@nxp.com>
> M: Hemant Agrawal <hemant.agrawal@nxp.com>
> -T: git://dpdk.org/next/dpdk-next-crypto
> +T: git://dpdk.org/next/dpdk-next-baseband
> F: drivers/baseband/la12xx/
> F: doc/guides/bbdevs/la12xx.rst
> F: doc/guides/bbdevs/features/la12xx.ini
Acked-by: Fan Zhang <fanzhang.oss@gmail.com>
next prev parent reply other threads:[~2022-12-05 10:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 7:59 Akhil Goyal
2022-12-05 10:57 ` Hemant Agrawal
2022-12-05 10:58 ` Zhang, Fan [this message]
2022-12-06 0:13 ` Chautru, Nicolas
2022-12-08 9:46 ` Maxime Coquelin
2022-12-08 11:23 ` 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=b14d05a6-a5c1-c312-8ac2-b53d6da4259b@gmail.com \
--to=fanzhang.oss@gmail.com \
--cc=dev@dpdk.org \
/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).