From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-next@vger.kernel.org
Subject: linux-next inclusion request for DRBD
Date: Sun, 15 Mar 2026 22:28:38 +0100 [thread overview]
Message-ID: <0b11c582-ef6d-4998-94fb-3ff606903481@linbit.com> (raw)
Hello,
we are currently in the process of getting version 9 of the DRBD driver
upstream. As this is rather complex and requires some large changes, we
would like to have the tree added to linux-next first. The tree is
available at:
https://github.com/LINBIT/linux-drbd drbd-next
We will keep this branch updated during the next few release cycles
until the patches actually land.
Please add the DRBD maintainers as contacts.
M: Philipp Reisner <philipp.reisner@linbit.com>
M: Lars Ellenberg <lars.ellenberg@linbit.com>
M: Christoph Böhmwalder <christoph.boehmwalder@linbit.com>
Thank you!
Best regards,
Christoph
--
Christoph Böhmwalder
LINBIT | Keeping the Digital World Running
DRBD HA — Disaster Recovery — Software defined Storage
next reply other threads:[~2026-03-15 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 21:28 Christoph Böhmwalder [this message]
2026-03-16 12:56 ` linux-next inclusion request for DRBD 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=0b11c582-ef6d-4998-94fb-3ff606903481@linbit.com \
--to=christoph.boehmwalder@linbit.com \
--cc=broonie@kernel.org \
--cc=linux-next@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