public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: io-uring@vger.kernel.org
Cc: asml.silence@gmail.com
Subject: [PATCH 1/1] io_uring: move zcrx into a separate branch
Date: Sun, 17 Aug 2025 23:43:14 +0100	[thread overview]
Message-ID: <989528e611b51d71fb712691ebfb76d2059ba561.1755461246.git.asml.silence@gmail.com> (raw)

Keep zcrx next changes in a separate branch. It was more productive this
way past month and will simplify the workflow for already lined up
changes requiring cross tree patches, specifically netdev. The current
changes can still target the generic io_uring tree as there are no
strong reasons to keep it separate. It'll also be using the io_uring
mailing list.

Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
---
 MAINTAINERS | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index fe168477caa4..d9e4ab173000 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -12870,6 +12870,14 @@ F:	include/uapi/linux/io_uring.h
 F:	include/uapi/linux/io_uring/
 F:	io_uring/
 
+IO_URING ZCRX
+M:	Pavel Begunkov <asml.silence@gmail.com>
+L:	io-uring@vger.kernel.org
+T:	git https://github.com/isilence/linux.git zcrx/for-next
+T:	git git://git.kernel.dk/linux-block
+S:	Maintained
+F:	io_uring/zcrx.*
+
 IPMI SUBSYSTEM
 M:	Corey Minyard <corey@minyard.net>
 L:	openipmi-developer@lists.sourceforge.net (moderated for non-subscribers)
-- 
2.49.0


             reply	other threads:[~2025-08-17 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-17 22:43 Pavel Begunkov [this message]
2025-08-18 15:24 ` [PATCH 1/1] io_uring: move zcrx into a separate branch Jens Axboe
2025-08-18 16:44   ` Pavel Begunkov
2025-08-20 18:20 ` 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=989528e611b51d71fb712691ebfb76d2059ba561.1755461246.git.asml.silence@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=io-uring@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