public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: David Wei <dw@davidwei.uk>
Cc: io-uring@vger.kernel.org, netdev@vger.kernel.org,
	Pavel Begunkov <asml.silence@gmail.com>,
	Mina Almasry <almasrymina@google.com>
Subject: Re: [PATCH 1/1] io_uring zcrx: add MAINTAINERS entry
Date: Tue, 21 Oct 2025 16:39:59 -0700	[thread overview]
Message-ID: <20251021163959.5040b7d6@kernel.org> (raw)
In-Reply-To: <20251021202944.3877502-1-dw@davidwei.uk>

On Tue, 21 Oct 2025 13:29:44 -0700 David Wei 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.

Thanks David! Not sure how to read the double T, I expected the entry
to be more of a copy of the existing IO_URING one. But it's a step
forward so if Jens is happy with this:

Acked-by: Jakub Kicinski <kuba@kernel.org>

  parent reply	other threads:[~2025-10-21 23:40 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
2025-10-21 23:39 ` Jakub Kicinski [this message]
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=20251021163959.5040b7d6@kernel.org \
    --to=kuba@kernel.org \
    --cc=almasrymina@google.com \
    --cc=asml.silence@gmail.com \
    --cc=dw@davidwei.uk \
    --cc=io-uring@vger.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