Re: [PATCH 00/20] DRBD 9 rework

[Jens Axboe <axboe@kernel.dk>]

On 4/3/26 7:24 AM, Christoph B?hmwalder wrote:
> On Thu, Apr 02, 2026 at 07:30:35PM -0600, Jens Axboe wrote:
>> On 3/27/26 4:38 PM, Christoph B?hmwalder wrote:
>>> As discussed (context: [0]), here is the first version of our DRBD 9
>>> rework series, intended for for-next via for-7.1/drbd.
>>
>> Will you fixup the kerneldoc (nits) and the assigned-but-not-read
>> issues and send out a new version? Also looks this series doesn't
>> actually apply to for-7.1/block, patch 12 fails.
>>
>> -- 
>> Jens Axboe
> 
> Right, the recent genl changes now cause a conflict. I'm rebasing now.
> The nits are already incorporated and will land with v2.
> 
> Just for my own planning: what does your timing cycle look like for the
> -next branch? I assume you also want to have that ready before the merge
> window opens? Or is the schedule for -next more liberal?

There's no timing for that branch, it always exists and has whatever is
pending for both the current and next release. Since linux-next rebases
every day, my for-next is also quite often rebased as it's just pulling
in everything that is pending. Hence there's no timing to worry about
here, it'll get updated daily basically as patches flow into various
branches.

-- 
Jens Axboe