public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, me@pmachata.org, jmaloy@redhat.com,
	parav@nvidia.com, elic@nvidia.com,
	Nikolay Aleksandrov <razor@blackwall.org>,
	leonro@nvidia.com
Subject: Re: [PATCH iproute2] Add MAINTAINERS file
Date: Thu, 11 May 2023 08:05:40 +0200	[thread overview]
Message-ID: <ZFyFtHNjcxOz0Ayp@nanopsycho> (raw)
In-Reply-To: <20230510210040.42325-1-stephen@networkplumber.org>

Wed, May 10, 2023 at 11:00:40PM CEST, stephen@networkplumber.org 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>
>Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>---
> MAINTAINERS | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 49 insertions(+)
> create mode 100644 MAINTAINERS
>
>diff --git a/MAINTAINERS b/MAINTAINERS
>new file mode 100644
>index 000000000000..fa720f686ba8
>--- /dev/null
>+++ b/MAINTAINERS
>@@ -0,0 +1,49 @@
>+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/*
>+
>+Device Link - devlink

It's actually just "Devlink". I don't think we have "device link"
anywhere.


>+M: Jiri Pirko <jiri@resnulli.us>
>+F: devlink/*
>+
>+Transparent Inter-Process Communication - Tipc
>+M: Jon Maloy <jmaloy@redhat.com>
>+F: tipc/*
>+
>+Virtual Datapath Accelration - Vdpa
>+M: Parav Pandit <parav@nvidia.com>
>+M: Eli Cohen <elic@nvidia.com>
>+F: vdpa/*
>-- 

What about "rdma"? I think Leon is a fit for that area.

Overall, good idea to have this!

Thanks!



  reply	other threads:[~2023-05-11  6:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10 21:00 [PATCH iproute2] Add MAINTAINERS file Stephen Hemminger
2023-05-11  6:05 ` Jiri Pirko [this message]
2023-05-11  7:02 ` Leon Romanovsky
2023-05-11 13:39 ` Petr Machata
2023-05-11 14:21 ` Parav Pandit

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=ZFyFtHNjcxOz0Ayp@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=elic@nvidia.com \
    --cc=jmaloy@redhat.com \
    --cc=leonro@nvidia.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