DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ugendreshwar Kudupudi <ukudupudi@marvell.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] maintainers: added liquidio driver maintainer
Date: Mon, 4 Jan 2021 13:55:27 +0000	[thread overview]
Message-ID: <25f4f2fe-dadf-1b6c-4939-fe489a42c504@intel.com> (raw)
In-Reply-To: <1608725107-5380-1-git-send-email-ukudupudi@marvell.com>

On 12/23/2020 12:05 PM, Ugendreshwar Kudupudi wrote:
> Added Marvell LiquidIO Driver Maintainer
> 
> Signed-off-by: Ugendreshwar Kudupudi <ukudupudi@marvell.com>
> ---
>   MAINTAINERS | 5 ++---
>   1 file changed, 2 insertions(+), 3 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index eafe9f8c4..a8d68f7ed 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -616,9 +616,8 @@ F: drivers/net/thunderx/
>   F: doc/guides/nics/thunderx.rst
>   F: doc/guides/nics/features/thunderx.ini
>   
> -Cavium LiquidIO - UNMAINTAINED

The driver is marked as unmaintained because of the missing close/remove 
implementation at first place.
Can you please update that part first before removing the unmaintained tag.

Both remove() and close() should free the driver allocated resources, and both 
should ensure device is stopped first. Also remove() can be called after close() 
called, please check other samples too.

> -M: Shijith Thotton <sthotton@marvell.com>
> -M: Srisivasubramanian Srinivasan <srinivasan@marvell.com>
> +Cavium LiquidIO
> +M: Ugendreshwar Kudupudi <ukudupudi@marvell.com>

Welcome Ugendreshwar, can Shijith and Srisivasubramanian also ack this patch?

>   T: git://dpdk.org/next/dpdk-next-net-mrvl
>   F: drivers/net/liquidio/
>   F: doc/guides/nics/liquidio.rst
> 


  reply	other threads:[~2021-01-04 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-23 12:05 Ugendreshwar Kudupudi
2021-01-04 13:55 ` Ferruh Yigit [this message]
2021-01-05  5:02 Shijith Thotton
2021-02-22  5:48 ` Ugendreshwar Kudupudi

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=25f4f2fe-dadf-1b6c-4939-fe489a42c504@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=ukudupudi@marvell.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).