From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Simon Horman <horms@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH RFC net 2/2] MAINTAINERS: Add headers and mailing list to UDP section
Date: Fri, 04 Oct 2024 11:25:12 -0400 [thread overview]
Message-ID: <670008d892bf9_c21242947e@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20241004-maint-net-hdrs-v1-2-41fd555aacc5@kernel.org>
Simon Horman wrote:
> Add netdev mailing list and some more udp.h headers to the UDP section.
> This is now more consistent with the TCP section.
>
> Signed-off-by: Simon Horman <horms@kernel.org>
Acked-by: Willem de Bruijn <willemb@google.com>
Also a reminder that maintainer and reviewer roles are not fixed,
and open to regular contributors to this code.
next prev parent reply other threads:[~2024-10-04 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 10:03 [PATCH RFC net 0/2] MAINTAINERS: Networking file coverage updates Simon Horman
2024-10-04 10:03 ` [PATCH RFC net 1/2] MAINTAINERS: consistently exclude wireless files from NETWORKING [GENERAL] Simon Horman
2024-10-04 14:32 ` Johannes Berg
2024-10-04 15:27 ` Kalle Valo
2024-10-07 14:13 ` Simon Horman
2024-10-07 17:30 ` Johannes Berg
2024-10-07 17:41 ` Kalle Valo
2024-10-07 18:03 ` Johannes Berg
2024-10-09 8:43 ` Simon Horman
2024-10-04 10:03 ` [PATCH RFC net 2/2] MAINTAINERS: Add headers and mailing list to UDP section Simon Horman
2024-10-04 15:25 ` Willem de Bruijn [this message]
2024-10-04 22:42 ` [PATCH RFC net 0/2] MAINTAINERS: Networking file coverage updates 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=670008d892bf9_c21242947e@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.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 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).