From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Simon Horman <horms@kernel.org>, Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
edumazet@google.com, pabeni@redhat.com, andrew+netdev@lunn.ch,
kuniyu@amazon.com, willemb@google.com
Subject: Re: [PATCH net 2/3] MAINTAINERS: add a general entry for BSD sockets
Date: Mon, 03 Feb 2025 09:30:14 -0500 [thread overview]
Message-ID: <67a0d2f6a14a1_8d5e29431@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20250203105408.GD234677@kernel.org>
Simon Horman wrote:
> On Sat, Feb 01, 2025 at 05:47:27PM -0800, Jakub Kicinski wrote:
> > Create a MAINTAINERS entry for BSD sockets. List the top 3
>
> 4?
>
> > reviewers as maintainers. The entry is meant to cover core
> > socket code (of which there isn't much) but also reviews
> > of any new socket families.
> >
> > Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> Reviewed-by: Simon Horman <horms@kernel.org>
Acked-by: Willem de Bruijn <willemb@google.com>
next prev parent reply other threads:[~2025-02-03 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 1:47 [PATCH net 0/3] MAINTAINERS: recognize Kuniyuki Iwashima as a maintainer Jakub Kicinski
2025-02-02 1:47 ` [PATCH net 1/3] MAINTAINERS: add Kuniyuki Iwashima to TCP reviewers Jakub Kicinski
2025-02-03 9:10 ` Eric Dumazet
2025-02-02 1:47 ` [PATCH net 2/3] MAINTAINERS: add a general entry for BSD sockets Jakub Kicinski
2025-02-03 10:54 ` Simon Horman
2025-02-03 14:30 ` Willem de Bruijn [this message]
2025-02-02 1:47 ` [PATCH net 3/3] MAINTAINERS: add entry for UNIX sockets Jakub Kicinski
2025-02-03 10:54 ` Simon Horman
2025-02-03 20:00 ` [PATCH net 0/3] MAINTAINERS: recognize Kuniyuki Iwashima as a maintainer Kuniyuki Iwashima
2025-02-03 21:30 ` patchwork-bot+netdevbpf
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=67a0d2f6a14a1_8d5e29431@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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).