netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Habets <habetsm.xilinx@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, me@pmachata.org, jiri@resnulli.us,
	jmaloy@redhat.com, parav@nvidia.com,
	Nikolay Aleksandrov <razor@blackwall.org>
Subject: Re: [PATCH iproute2 v2] Add MAINTAINERS file
Date: Fri, 12 May 2023 08:23:01 +0100	[thread overview]
Message-ID: <ZF3pVX118sExgpXg@gmail.com> (raw)
In-Reply-To: <20230511160002.25439-1-stephen@networkplumber.org>

On Thu, May 11, 2023 at 09:00:02AM -0700, Stephen Hemminger wrote:
> Record the maintainers of subsections of iproute2.
> The subtree maintainers are based off of most recent current
> patches and maintainer of kernel portion of that subsystem.
> 
> Acked-by: Nikolay Aleksandrov <razor@blackwall.org>
> Acked-by: Petr Machata <me@pmachata.org> # For DCB
> Acked-by: Parav Pandit <parav@nvidia.com>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  MAINTAINERS | 53 +++++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 53 insertions(+)
>  create mode 100644 MAINTAINERS
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> new file mode 100644
> index 000000000000..ec193fd8459a
> --- /dev/null
> +++ b/MAINTAINERS
> @@ -0,0 +1,53 @@
> +Iproute2 Maintainers
> +====================
> +
> +The file provides a set of names that are are able to help
> +review patches and answer questions. This is in addition to
> +the netdev@vger.kernel.org mailing list used for all iproute2
> +and kernel networking.
> +
> +Descriptions of section entries:
> +
> +	M: Maintainer's Full Name <address@domain>
> +	T: Git tree location.
> +	F: Files and directories with wildcard patterns.
> +	   A trailing slash includes all files and subdirectory files.
> +	   A wildcard includes all files but not subdirectories.
> +	   One pattern per line. Multiple F: lines acceptable.
> +
> +Main Branch
> +M: Stephen Hemminger <stephen@networkplumber.org>
> +T: git://git.kernel.org/pub/scm/network/iproute2/iproute2.git
> +L: netdev@vger.kernel.org
> +
> +Next Tree
> +M: David Ahern <dsahern@gmail.com>
> +T: git://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git
> +L: netdev@vger.kernel.org
> +
> +Ethernet Bridging - bridge
> +M: Roopa Prabhu <roopa@nvidia.com>
> +M: Nikolay Aleksandrov <razor@blackwall.org>
> +L: bridge@lists.linux-foundation.org (moderated for non-subscribers)
> +F: bridge/*
> +
> +Data Center Bridging - dcb
> +M: Petr Machata <me@pmachata.org>
> +F: dcb/*
> +
> +devlink
> +M: Jiri Pirko <jiri@resnulli.us>
> +F: devlink/*
> +
> +Remote DMA - rdma
> +M: Leon Romanovsky <leon@kernel.org>
> +F: rdma/*
> +
> +Transparent Inter-Process Communication - tipc
> +M: Jon Maloy <jmaloy@redhat.com>
> +F: tipc/*
> +
> +Virtual Datapath Accelration - vdpa

Typo here, it should say Acceleration.

Martin

> +M: Parav Pandit <parav@nvidia.com>
> +M: Eli Cohen <elic@nvidia.com>
> +F: vdpa/*
> -- 
> 2.39.2
> 

  reply	other threads:[~2023-05-12  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 16:00 [PATCH iproute2 v2] Add MAINTAINERS file Stephen Hemminger
2023-05-12  7:23 ` Martin Habets [this message]
2023-05-12 11:27 ` Jiri Pirko

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=ZF3pVX118sExgpXg@gmail.com \
    --to=habetsm.xilinx@gmail.com \
    --cc=jiri@resnulli.us \
    --cc=jmaloy@redhat.com \
    --cc=me@pmachata.org \
    --cc=netdev@vger.kernel.org \
    --cc=parav@nvidia.com \
    --cc=razor@blackwall.org \
    --cc=stephen@networkplumber.org \
    /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).