From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-f44.google.com (mail-wm1-f44.google.com [209.85.128.44]) by mail19.linbit.com (LINBIT Mail Daemon) with ESMTP id 314961622C4 for ; Fri, 3 Apr 2026 15:24:42 +0200 (CEST) Received: by mail-wm1-f44.google.com with SMTP id 5b1f17b1804b1-4853e1ce427so24151555e9.3 for ; Fri, 03 Apr 2026 06:24:42 -0700 (PDT) Date: Fri, 3 Apr 2026 15:24:39 +0200 From: Christoph =?utf-8?Q?B=C3=B6hmwalder?= To: Jens Axboe Subject: Re: [PATCH 00/20] DRBD 9 rework Message-ID: References: <20260327223820.2244227-1-christoph.boehmwalder@linbit.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Cc: linux-block@vger.kernel.org, Lars Ellenberg , Philipp Reisner , linux-kernel@vger.kernel.org, drbd-dev@lists.linbit.com List-Id: "*Coordination* of development, patches, contributions -- *Questions* \(even to developers\) go to drbd-user, please." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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? Thanks, Christoph