From: Thomas Monjalon <thomas@monjalon.net>
To: Nikhil Rao <nikhil.rao@intel.com>
Cc: dev@dpdk.org, jerinj@marvell.com, jay.jayatheerthan@intel.com,
bruce.richardson@intel.com, david.marchand@redhat.com,
ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH] maintainers: update maintainers for event ethdev rx/tx adapters
Date: Thu, 24 Sep 2020 01:45:05 +0200 [thread overview]
Message-ID: <2454192.SI5LlRtHpv@thomas> (raw)
In-Reply-To: <1598407326-5801-1-git-send-email-nikhil.rao@intel.com>
> Jay is the new maintainer since Nikhil no longer works on DPDK.
>
> Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
[...]
> Eventdev Ethdev Rx Adapter API
> -M: Nikhil Rao <nikhil.rao@intel.com>
> +M: Jay Jayatheerthan <jay.jayatheerthan@intel.com>
> T: git://dpdk.org/next/dpdk-next-eventdev
> F: lib/librte_eventdev/*eth_rx_adapter*
> F: app/test/test_event_eth_rx_adapter.c
> F: doc/guides/prog_guide/event_ethernet_rx_adapter.rst
>
> Eventdev Ethdev Tx Adapter API
> -M: Nikhil Rao <nikhil.rao@intel.com>
> +M: Jay Jayatheerthan <jay.jayatheerthan@intel.com>
> T: git://dpdk.org/next/dpdk-next-eventdev
> F: lib/librte_eventdev/*eth_tx_adapter*
> F: app/test/test_event_eth_tx_adapter.c
That's good you've found a replacement.
I don't know how/when applying this patch given Jay
is not yet showing experience with this code.
The contribution guide says:
"
Maintainers should have demonstrated a reasonable level
of contributions or reviews to the component area.
"
http://doc.dpdk.org/guides/contributing/patches.html#maintainers-and-sub-trees
Any hint or opinion please?
next prev parent reply other threads:[~2020-09-23 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 2:02 [dpdk-dev] [PATCH] maintainers: update maintainers for event ethdev rx/tx adapters Nikhil Rao
2020-09-23 23:45 ` Thomas Monjalon [this message]
2020-11-27 9:40 ` 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=2454192.SI5LlRtHpv@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.com \
--cc=nikhil.rao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.