public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>,
	"Philipp Reisner" <philipp.reisner@linbit.com>,
	"Lars Ellenberg" <lars.ellenberg@linbit.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the block tree with the drbd tree
Date: Wed, 25 Mar 2026 15:41:00 +0000	[thread overview]
Message-ID: <acQCDMhGqwhzLuzt@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

Hi all,

Today's linux-next merge of the block tree got a conflict in:

  drivers/block/drbd/drbd_nl.c

between commit:

  ffa847f8ff11d ("drbd: rework netlink interface for DRBD 9 multi-peer config")

from the drbd tree and commit:

  630bbba45cfd3 ("drbd: use genl pre_doit/post_doit")

from the block tree.

These changes are both quite large and the conflicts substantial,
ffa847f8ff11d ("drbd: rework netlink interface for DRBD 9 multi-peer
config") in particular has a diffstat of:

 drivers/block/drbd/drbd_nl.c | 7260 ++++++++++++++++++++++++++++++------------
 1 file changed, 5167 insertions(+), 2093 deletions(-)

which would be enormous even for a non-mechanical change, based on the
size and a glance over the changelog it seems clear to me that it should
be split up into a series of patches.  This would make resolving the
conflicts much more tractable as it would be clearer what each change is
trying to accomplish.

630bbba45cfd3 ("drbd: use genl pre_doit/post_doit") is much less of a
concern as while it's fairly large it is mostly mechanical.

Since I've got no confidence in my ability to do so rather than
resolving this I have marked the DRBD driver as BROKEN for today
(there's a half completed merge in the tree which shows how far I got)
and I will reorder the drbd tree after the block tree going forward
since it seems to feed into there.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-03-25 15:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 15:41 Mark Brown [this message]
2026-03-25 15:56 ` linux-next: manual merge of the block tree with the drbd tree Jens Axboe
2026-03-25 16:13   ` Mark Brown
2026-03-25 16:07 ` Christoph Böhmwalder
2026-03-25 16:30   ` Jens Axboe
2026-03-25 16:47     ` Christoph Böhmwalder
2026-03-25 16:57       ` Mark Brown
2026-03-25 17:33         ` Christoph Böhmwalder
2026-03-25 17:55           ` Mark Brown
2026-03-25 18:35       ` Jens Axboe
2026-03-25 16:25 ` Mark Brown

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=acQCDMhGqwhzLuzt@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=christoph.boehmwalder@linbit.com \
    --cc=lars.ellenberg@linbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=philipp.reisner@linbit.com \
    /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