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, Nikolay Aleksandrov <razor@blackwall.org>
Subject: Re: [PATCH iproute2 v2] Add MAINTAINERS file
Date: Fri, 12 May 2023 13:27:45 +0200 [thread overview]
Message-ID: <ZF4isc8xGwht6zpC@nanopsycho> (raw)
In-Reply-To: <20230511160002.25439-1-stephen@networkplumber.org>
Thu, May 11, 2023 at 06:00:02PM 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>
>Acked-by: Petr Machata <me@pmachata.org> # For DCB
>Acked-by: Parav Pandit <parav@nvidia.com>
Acked-by: Jiri Pirko <jiri@nvidia.com>
prev parent reply other threads:[~2023-05-12 11:27 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
2023-05-12 11:27 ` Jiri Pirko [this message]
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=ZF4isc8xGwht6zpC@nanopsycho \
--to=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).