public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCH 1/1] io_uring: move zcrx into a separate branch
Date: Mon, 20 Oct 2025 12:01:16 -0600	[thread overview]
Message-ID: <12e1e244-4b85-4916-83ab-3358b83d8c3c@kernel.dk> (raw)
In-Reply-To: <b10cb42e-0fb5-4616-bb44-db3e7172ccdc@gmail.com>

On 10/20/25 11:41 AM, Pavel Begunkov wrote:
> On 10/20/25 18:07, Jens Axboe wrote:
>> On 10/17/25 6:37 AM, Pavel Begunkov wrote:
>>> On 8/20/25 19:20, Jens Axboe wrote:
>>>>
>>>> On Sun, 17 Aug 2025 23:43:14 +0100, Pavel Begunkov wrote:
>>>>> 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.
>>>>>
>>>>> [...]
>>>>
>>>> Applied, thanks!
>>>
>>> Did it get dropped in the end? For some reason I can't find it.
>>
>> A bit hazy, but I probably did with the discussions on the netdev side
>> too as they were ongoing.
> 
> The ones where my work is maliciously blocked with a good email
> trace to prove that? How is that relevant though?

I have no horse in that game so don't know which thread(s) that is (nor
does it sound like I need to know), I just recall Mina and/or someone
else having patches for this too. Hence I dropped it to get everyone
come to an agreement on what the appropriate entry would be.

FWIW, I don't think there's much point to listing a separate branch.
It's all supposed to go upstream to the main tree sooner rather than
later, once it's ready. And since it's basically just you working on the
zcrx bits, there's no risk of conflicts. If there was a conflict, then
yeah we'd just resolve it and route things appropriately. But it also
doesn't really matter to me what's listed in there, as long as things
are on the list as well. And iirc the netdev side was the same, they
just want to ensure they see patches for zcrx. For me, the entry was
more about ensuring you get CC'ed on relevant patches.

Which is why I figured that you and the netdev side would discuss this
and come up with an entry that everybody was happy with, then we can get
that upstream.

-- 
Jens Axboe

  reply	other threads:[~2025-10-20 18:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-17 22:43 [PATCH 1/1] io_uring: move zcrx into a separate branch Pavel Begunkov
2025-08-18 15:24 ` Jens Axboe
2025-08-18 16:44   ` Pavel Begunkov
2025-08-20 18:20 ` Jens Axboe
2025-10-17 12:37   ` Pavel Begunkov
2025-10-20 17:07     ` Jens Axboe
2025-10-20 17:41       ` Pavel Begunkov
2025-10-20 18:01         ` Jens Axboe [this message]
2025-10-20 18:34           ` Pavel Begunkov
2025-10-21 13:44             ` Pavel Begunkov
2025-10-21 15:42               ` Jens Axboe
2025-10-21 18:45                 ` Pavel Begunkov
2025-10-21 18:46                   ` 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=12e1e244-4b85-4916-83ab-3358b83d8c3c@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=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