From: Nikolay Aleksandrov <razor@blackwall.org>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>
Subject: Re: [PATCH net] MAINTAINERS: update the IPv4/IPv6 entry and add Ido Schimmel
Date: Wed, 29 Apr 2026 12:14:22 +0300 [thread overview]
Message-ID: <2dc013c8-8ef4-48af-90fd-1ce6ea3b893a@blackwall.org> (raw)
In-Reply-To: <20260428203924.1229169-1-kuba@kernel.org>
On 28/04/2026 23:39, Jakub Kicinski wrote:
> The IPv4/IPv6 and routing code is not very well separated from
> the TCP/UDP code. Scope it down properly by providing a more
> accurate file list, instead of net/ipv4/ and net/ipv6/
>
> Now that the entry is more accurately representing layer 3
> and routing merge in the nexthop entry into it.
>
> Add Ido Schimmel as a co-maintainer, Ido's git history speaks
> for itself.
>
> Reviewed-by: David Ahern <dsahern@kernel.org>
> Reviewed-by: Ido Schimmel <idosch@nvidia.com>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
> MAINTAINERS | 63 +++++++++++++++++++++++++++++++++++++++--------------
> 1 file changed, 47 insertions(+), 16 deletions(-)
>
Wohoo, great!
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
next prev parent reply other threads:[~2026-04-29 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 20:39 [PATCH net] MAINTAINERS: update the IPv4/IPv6 entry and add Ido Schimmel Jakub Kicinski
2026-04-29 9:14 ` Nikolay Aleksandrov [this message]
2026-04-30 0:40 ` patchwork-bot+netdevbpf
2026-05-12 12:27 ` Geert Uytterhoeven
2026-05-12 15:19 ` Jakub Kicinski
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=2dc013c8-8ef4-48af-90fd-1ce6ea3b893a@blackwall.org \
--to=razor@blackwall.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.