DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>,
	Pascal Mazon <pascal.mazon@6wind.com>,
	Moti Haimovsky <motih@mellanox.com>,
	Ophir Munk <ophirmu@nvidia.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>,
	Asaf Penso <asafp@nvidia.com>,
	David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH] tap:remove maintainer
Date: Tue, 18 Jan 2022 09:29:37 +0000	[thread overview]
Message-ID: <df9c54f7-fca4-92ae-d272-087f43c8fe57@intel.com> (raw)
In-Reply-To: <f1e5aad6-dcf4-7b80-5f50-062b474ed8dd@intel.com>

On 12/6/2021 2:12 PM, Ferruh Yigit wrote:
> On 12/2/2021 5:15 PM, Wiles, Keith wrote:
>> I no longer have the bandwidth to support the TAP PMD, so I am
>> removing myself as the maintainer so as to not hold up commits.
>>
> 
> Thanks Keith, introducing this PMD and maintaining up until now, when
> you have more time we would like to see you back.
> 
> Meanwhile some features of the PMD like rte_flow, eBPF (for RSS),
> netlink, Rx interrupt, TC support, etc.. introduced by 6wind/Nvidia,
> and these features makes majority of the driver.
> 
> Pascal, Ophir, Moti, do you still have use cases for these features?
> Can you please help maintaining the driver?
> 
> Thanks,
> ferruh
> 
>> Signed-off-by: Wiles, Keith <keith.wiles@intel.com>

Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/main, thanks.

  parent reply	other threads:[~2022-01-18  9:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-02 17:15 Wiles, Keith
2021-12-06 14:12 ` Ferruh Yigit
2022-01-18  9:28   ` Ferruh Yigit
2022-01-18  9:29   ` Ferruh Yigit [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-02 17:00 Wiles, Keith

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=df9c54f7-fca4-92ae-d272-087f43c8fe57@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=asafp@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    --cc=motih@mellanox.com \
    --cc=ophirmu@nvidia.com \
    --cc=pascal.mazon@6wind.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).