From: Mina Almasry <almasrymina@google.com>
To: David Wei <dw@davidwei.uk>
Cc: io-uring@vger.kernel.org, netdev@vger.kernel.org,
Pavel Begunkov <asml.silence@gmail.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH 1/1] io_uring zcrx: add MAINTAINERS entry
Date: Tue, 21 Oct 2025 13:49:02 -0700 [thread overview]
Message-ID: <CAHS8izNuJUXnQCz6X4xMGu=fm2jZ5VO-d=57xC7epu3Bn5T5Gg@mail.gmail.com> (raw)
In-Reply-To: <20251021202944.3877502-1-dw@davidwei.uk>
On Tue, Oct 21, 2025 at 1:29 PM David Wei <dw@davidwei.uk> wrote:
>
> Same as [1] but also with netdev@ as an additional mailing list.
> io_uring zero copy receive is of particular interest to netdev
> participants too, given its tight integration to netdev core.
>
> With this updated entry, folks running get_maintainer.pl on patches that
> touch io_uring/zcrx.* will know to send it to netdev@ as well.
>
> Note that this doesn't mean all changes require explicit acks from
> netdev; this is purely for wider visibility and for other contributors
> to know where to send patches.
>
> [1]: https://lore.kernel.org/io-uring/989528e611b51d71fb712691ebfb76d2059ba561.1755461246.git.asml.silence@gmail.com/
>
> Signed-off-by: David Wei <dw@davidwei.uk>
Seems fine to me,
Reviewed-by: Mina Almasry <almasrymina@google.com>
--
Thanks,
Mina
next prev parent reply other threads:[~2025-10-21 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 20:29 [PATCH 1/1] io_uring zcrx: add MAINTAINERS entry David Wei
2025-10-21 20:49 ` Mina Almasry [this message]
2025-10-21 23:39 ` Jakub Kicinski
2025-10-22 11:38 ` Pavel Begunkov
2025-10-22 13:17 ` Jens Axboe
2025-10-22 14:25 ` Pavel Begunkov
2025-10-22 14:34 ` Jens Axboe
2025-10-22 17:01 ` Pavel Begunkov
2025-10-22 14:30 ` Keith Busch
2025-10-22 14:35 ` Jens Axboe
2025-10-22 17:06 ` Jens Axboe
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='CAHS8izNuJUXnQCz6X4xMGu=fm2jZ5VO-d=57xC7epu3Bn5T5Gg@mail.gmail.com' \
--to=almasrymina@google.com \
--cc=asml.silence@gmail.com \
--cc=dw@davidwei.uk \
--cc=io-uring@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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