Re: [zcrx-next 0/2] add support for synchronous refill

[Jens Axboe <axboe@kernel.dk>]

On 8/20/25 1:33 PM, Pavel Begunkov wrote:
> On 8/20/25 20:02, Jens Axboe wrote:
>> On 8/20/25 12:57 PM, Pavel Begunkov wrote:
>>> On 8/20/25 19:20, Jens Axboe wrote:
>>>>
>>>> On Sun, 17 Aug 2025 23:44:56 +0100, Pavel Begunkov wrote:
>>>>> Returning buffers via a ring is efficient but can cause problems
>>>>> when the ring doesn't have space. Add a way to return buffers
>>>>> synchronously via io_uring "register" syscall, which should serve
>>>>> as a slow fallback path.
>>>>>
>>>>> For a full branch with all relevant dependencies see
>>>>> https://github.com/isilence/linux.git zcrx/for-next
>>>>>
>>>>> [...]
>>>>
>>>> Applied, thanks!
>>>
>>> Leave these and other series out please. I sent them for
>>> review, but it'll be easier to keep in a branch and rebase
>>> it if necessary. I hoped tagging with zcrx-next would be
>>> good enough of a sign.
>>
>> Alright, but then please make it clear when you are sending
>> something out for merging.
> 
> That would be a pull request, should be obvious enough. Perhaps
> it'd make sense to tag for review only patches. Any preference
> what tag it should be or otherwise?

Please just send patches rather than a pull request. PRs get messed up
by people all the time, and there's no picking and choosing there, it's
all or nothing.

A review tag would be good in the subject, anything easily recognizable
should do it. Like for-review or whatever, doesn't matter to me.

-- 
Jens Axboe