DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"jerinjacobk@gmail.com" <jerinjacobk@gmail.com>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Mcnamara, John" <john.mcnamara@intel.com>
Subject: RE: [PATCH] maintainers: change maintainer for event ethdev Rx/Tx adapters
Date: Mon, 31 Oct 2022 11:05:20 +0000	[thread overview]
Message-ID: <DM6PR11MB3868C16E1C7204C5E93866E3A1379@DM6PR11MB3868.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2478570.4XsnlVU6TS@thomas>


> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Sunday, October 30, 2022 2:30 PM
> To: Naga Harish K, S V <s.v.naga.harish.k@intel.com>; Jayatheerthan, Jay
> <jay.jayatheerthan@intel.com>
> Cc: dev@dpdk.org; jerinjacobk@gmail.com; jerinj@marvell.com;
> dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>
> Subject: Re: [PATCH] maintainers: change maintainer for event ethdev Rx/Tx
> adapters
> 
> 21/10/2022 13:35, Jay Jayatheerthan:
> > Harish is the new maintainer of Rx/Tx adapters due to role change of Jay
> >
> > Signed-off-by: Jay Jayatheerthan <jay.jayatheerthan@intel.com>
> 
> Please could we have an approval from the new maintainer?
> An ack would make things clear and accepted.

Acked by: Naga Harish K S V <s.v.naga.harish.k@intel.com>

> 
> 


  reply	other threads:[~2022-10-31 11:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 11:35 Jay Jayatheerthan
2022-10-30  9:00 ` Thomas Monjalon
2022-10-31 11:05   ` Naga Harish K, S V [this message]
2022-10-31 16:16     ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2022-10-21 11:28 Jay Jayatheerthan

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=DM6PR11MB3868C16E1C7204C5E93866E3A1379@DM6PR11MB3868.namprd11.prod.outlook.com \
    --to=s.v.naga.harish.k@intel.com \
    --cc=dev@dpdk.org \
    --cc=jay.jayatheerthan@intel.com \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=john.mcnamara@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).