From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "Philipp Reisner" <philipp.reisner@linbit.com>,
"Lars Ellenberg" <lars@linbit.com>,
drbd-dev@lists.linux.dev, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>,
"Lars Ellenberg" <lars.ellenberg@linbit.com>
Subject: [PATCH 1/7] drbd: rename drbd_worker.c to drbd_sender.c
Date: Wed, 23 Sep 2026 16:06:02 +0200 [thread overview]
Message-ID: <20260923140608.1116713-2-christoph.boehmwalder@linbit.com> (raw)
In-Reply-To: <20260923140608.1116713-1-christoph.boehmwalder@linbit.com>
The "worker" thread has long since become the thread that sends data
and resync requests to the peer; the receiving side lives in
drbd_receiver.c. The out-of-tree DRBD 9 code base has called this file
drbd_sender.c for years.
Rename the file up front, with no content change, so that the upcoming
DRBD 9 rework of this thread shows up as a modification of one file
instead of the removal of one file and the addition of another.
Signed-off-by: Christoph Böhmwalder <christoph.boehmwalder@linbit.com>
---
drivers/block/drbd/Makefile | 2 +-
drivers/block/drbd/{drbd_worker.c => drbd_sender.c} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename drivers/block/drbd/{drbd_worker.c => drbd_sender.c} (100%)
diff --git a/drivers/block/drbd/Makefile b/drivers/block/drbd/Makefile
index 5faaa8a8e7f0..1a6dc0f482f5 100644
--- a/drivers/block/drbd/Makefile
+++ b/drivers/block/drbd/Makefile
@@ -1,6 +1,6 @@
# SPDX-License-Identifier: GPL-2.0-only
drbd-y := drbd_buildtag.o drbd_bitmap.o drbd_proc.o
-drbd-y += drbd_worker.o drbd_receiver.o drbd_req.o drbd_actlog.o
+drbd-y += drbd_sender.o drbd_receiver.o drbd_req.o drbd_actlog.o
drbd-y += drbd_main.o drbd_strings.o drbd_nl.o
drbd-y += drbd_interval.o drbd_state.o
drbd-y += drbd_nl_gen.o
diff --git a/drivers/block/drbd/drbd_worker.c b/drivers/block/drbd/drbd_sender.c
similarity index 100%
rename from drivers/block/drbd/drbd_worker.c
rename to drivers/block/drbd/drbd_sender.c
--
2.55.0
next prev parent reply other threads:[~2026-09-23 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 14:06 [PATCH 0/7] drbd: preparation for DRBD 9 Christoph Böhmwalder
2026-09-23 14:06 ` Christoph Böhmwalder [this message]
2026-09-23 14:06 ` [PATCH 2/7] drbd: modernize the file header comments Christoph Böhmwalder
2026-09-23 14:06 ` [PATCH 3/7] drbd: raise the socket buffer size limits to 128 MiB Christoph Böhmwalder
2026-09-23 14:06 ` [PATCH 4/7] drbd: raise the maximum resync rate to 8 GiB/s Christoph Böhmwalder
2026-09-23 14:06 ` [PATCH 5/7] drbd: replace the drbd_interval bitfields with a type and flags Christoph Böhmwalder
2026-09-23 14:06 ` [PATCH 6/7] drbd: move the packet name table to drbd_strings.c Christoph Böhmwalder
2026-09-23 14:06 ` [PATCH 7/7] drbd: rate limit log messages per object Christoph Böhmwalder
2026-11-09 17:22 ` [PATCH 0/7] drbd: preparation for DRBD 9 Christoph Böhmwalder
2026-11-09 17:40 ` Jens Axboe
2026-11-09 17:40 ` Jens Axboe
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=20260923140608.1116713-2-christoph.boehmwalder@linbit.com \
--to=christoph.boehmwalder@linbit.com \
--cc=axboe@kernel.dk \
--cc=drbd-dev@lists.linux.dev \
--cc=lars.ellenberg@linbit.com \
--cc=lars@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®