From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Akhil Goyal <gakhil@marvell.com>, dev@dpdk.org
Cc: thomas@monjalon.net, nicolas.chautru@intel.com, hemant.agrawal@nxp.com
Subject: Re: [PATCH] maintainers: split baseband from crypto tree
Date: Thu, 8 Dec 2022 10:46:08 +0100 [thread overview]
Message-ID: <adeb9b5d-ef10-f469-2f9e-f321c779b129@redhat.com> (raw)
In-Reply-To: <20221205075944.822372-1-gakhil@marvell.com>
Hi Akhil,
On 12/5/22 08:59, 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(-)
>
Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Thanks for having maintained baseband until now!
Maxime
next prev parent reply other threads:[~2022-12-08 9:46 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
2022-12-06 0:13 ` Chautru, Nicolas
2022-12-08 9:46 ` Maxime Coquelin [this message]
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=adeb9b5d-ef10-f469-2f9e-f321c779b129@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=nicolas.chautru@intel.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).