From: Christoph Hellwig <hch@lst.de>
To: Philipp Reisner <philipp.reisner@linbit.com>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
Jens Axboe <axboe@kernel.dk>
Cc: drbd-dev@lists.linbit.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: state of drbd in mainline
Date: Tue, 29 Mar 2022 09:06:18 +0200 [thread overview]
Message-ID: <20220329070618.GA20396@lst.de> (raw)
Hi all,
while I've been reworking large parts of the block layer over the
last months I've basically never gotten drbd reviews, and in general
drbd seems to be completely maintained upstream. Do we even have users
for it? Is it time to drop drbd from the kernel tree?
Thanks,
Christoph
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Philipp Reisner <philipp.reisner@linbit.com>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
drbd-dev@lists.linbit.com
Subject: [Drbd-dev] state of drbd in mainline
Date: Tue, 29 Mar 2022 09:06:18 +0200 [thread overview]
Message-ID: <20220329070618.GA20396@lst.de> (raw)
Hi all,
while I've been reworking large parts of the block layer over the
last months I've basically never gotten drbd reviews, and in general
drbd seems to be completely maintained upstream. Do we even have users
for it? Is it time to drop drbd from the kernel tree?
Thanks,
Christoph
next reply other threads:[~2022-03-29 7:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 7:06 Christoph Hellwig [this message]
2022-03-29 7:06 ` [Drbd-dev] state of drbd in mainline Christoph Hellwig
2022-03-29 7:22 ` Philipp Reisner
2022-03-29 7:32 ` Christoph Hellwig
2022-03-29 7:32 ` [Drbd-dev] " Christoph Hellwig
2022-03-29 7:50 ` Philipp Reisner
2022-03-29 7:50 ` [Drbd-dev] " Philipp Reisner
2022-03-29 12:29 ` Jens Axboe
2022-03-29 12:29 ` [Drbd-dev] " Jens Axboe
2022-03-29 15:44 ` Philipp Reisner
2022-03-29 15:44 ` [Drbd-dev] " Philipp Reisner
2022-03-29 15:52 ` Jens Axboe
2022-03-29 15:52 ` [Drbd-dev] " Jens Axboe
2022-03-30 15:23 ` Philipp Reisner
2022-03-30 15:23 ` [Drbd-dev] " Philipp Reisner
2022-03-30 18:06 ` Mike Snitzer
2022-03-30 18:06 ` [Drbd-dev] " Mike Snitzer
2022-03-30 18:24 ` Jens Axboe
2022-03-30 18:24 ` [Drbd-dev] " Jens Axboe
2022-03-30 19:31 ` Kiselev, Oleg
2022-03-30 19:31 ` Kiselev, Oleg
2022-03-30 20:21 ` Jens Axboe
2022-03-30 20:21 ` Jens Axboe
2022-03-29 20:01 ` Wolfgang Walter
2022-03-29 20:01 ` Wolfgang Walter
2022-03-29 7:24 ` Philipp Reisner
2022-03-29 7:24 ` [Drbd-dev] " Philipp Reisner
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=20220329070618.GA20396@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.