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 --- 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 +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 L: openipmi-developer@lists.sourceforge.net (moderated for non-subscribers) -- 2.49.0