From: Thomas Monjalon <thomas@monjalon.net>
To: s.v.naga.harish.k@intel.com,
Jay Jayatheerthan <jay.jayatheerthan@intel.com>
Cc: dev@dpdk.org, jerinjacobk@gmail.com, jerinj@marvell.com,
dev@dpdk.org, john.mcnamara@intel.com
Subject: Re: [PATCH] maintainers: change maintainer for event ethdev Rx/Tx adapters
Date: Sun, 30 Oct 2022 10:00:21 +0100 [thread overview]
Message-ID: <2478570.4XsnlVU6TS@thomas> (raw)
In-Reply-To: <20221021113535.820-1-jay.jayatheerthan@intel.com>
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.
next prev parent reply other threads:[~2022-10-30 9:00 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 [this message]
2022-10-31 11:05 ` Naga Harish K, S V
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=2478570.4XsnlVU6TS@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=john.mcnamara@intel.com \
--cc=s.v.naga.harish.k@intel.com \
/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).