DPDK patches and discussions
 help / color / mirror / Atom feed
From: Asaf Penso <asafp@mellanox.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] maintainers: update for Mellanox
Date: Thu, 4 Jul 2019 19:44:27 +0000	[thread overview]
Message-ID: <AM6PR05MB661577615738E43039523E40C0FA0@AM6PR05MB6615.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <aad19e7a-2ca0-9132-ff58-dc5c5e66d18d@intel.com>

Shahaf, thank you very much for all the wonderful support and work during past years.
I wish you many successes and challenges and for sure will see you around 😊

Raslan, welcome and good luck. I'm confident you will do a great job!

Regards,
Asaf Penso

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Ferruh Yigit
> Sent: Thursday, July 4, 2019 7:23 PM
> To: Shahaf Shuler <shahafs@mellanox.com>; Thomas Monjalon
> <thomas@monjalon.net>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] maintainers: update for Mellanox
> 
> On 7/4/2019 11:01 AM, Shahaf Shuler wrote:
> > Due to position change, cannot be a full time maintainer anymore.
> > The git tree dpdk-next-net-mlx will be managed by Raslan, as approved by
> > the DPDK Technical Board.
> > For mlx5 PMD, Slava is added as additional maintainer.
> >
> > Will continue to be invovled in the DPDK community in different ways.
> >
> > Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> 
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
> 
> Applied to dpdk-next-net/master, thanks.
> 
> 
> Thanks Shahaf for all the work! Best luck with new role & see you around...
> 
> And welcome Raslan :)

      reply	other threads:[~2019-07-04 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 10:01 Shahaf Shuler
2019-07-04 16:22 ` Ferruh Yigit
2019-07-04 19:44   ` Asaf Penso [this message]

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=AM6PR05MB661577615738E43039523E40C0FA0@AM6PR05MB6615.eurprd05.prod.outlook.com \
    --to=asafp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=shahafs@mellanox.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).