DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ori Kam <orika@mellanox.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] maintainers: resign from flow API maintenance
Date: Thu, 9 Jan 2020 07:42:12 +0000	[thread overview]
Message-ID: <AM4PR05MB3425D299A0D7F01C3FE37B86DB390@AM4PR05MB3425.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200108100830.29456-1-adrien.mazarguil@6wind.com>



> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Adrien Mazarguil
> Sent: Wednesday, January 8, 2020 12:10 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: [dpdk-dev] [PATCH] maintainers: resign from flow API maintenance
> 
> Unfortunately due to lack of time, I've been unable to even participate to
> flow API discussions for several months. Better make it official since this
> is not going to improve anytime soon.
> 
> This doesn't mean I won't contribute to rte_flow in the future!
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
> ---

Acked-by: Ori Kam <orika@mellanox.com>
Thanks,
Ori 


>  MAINTAINERS | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 96fc89dc48..7355d88c95 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -370,7 +370,6 @@ F: devtools/test-null.sh
>  F: doc/guides/prog_guide/switch_representation.rst
> 
>  Flow API
> -M: Adrien Mazarguil <adrien.mazarguil@6wind.com>
>  M: Ori Kam <orika@mellanox.com>
>  T: git://dpdk.org/next/dpdk-next-net
>  F: app/test-pmd/cmdline_flow.c
> --
> 2.20.1

  reply	other threads:[~2020-01-09  7:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 10:10 Adrien Mazarguil
2020-01-09  7:42 ` Ori Kam [this message]
2020-01-21 17:59   ` 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=AM4PR05MB3425D299A0D7F01C3FE37B86DB390@AM4PR05MB3425.eurprd05.prod.outlook.com \
    --to=orika@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=stable@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).