From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org,
"Lars Ellenberg" <lars.ellenberg@linbit.com>,
"Philipp Reisner" <philipp.reisner@linbit.com>,
linux-block@vger.kernel.org,
"Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
Subject: [PATCH 0/3] DRBD file structure reorganization
Date: Fri, 9 Dec 2022 15:55:01 +0100 [thread overview]
Message-ID: <20221209145504.2273072-1-christoph.boehmwalder@linbit.com> (raw)
To make our lives easier when sending future, more complex patches,
we want to align the file structure as best as possible with what we
have in the out-of-tree module.
Christoph Böhmwalder (3):
drbd: split off drbd_buildtag into separate file
drbd: drop API_VERSION define
drbd: split off drbd_config into separate file
drivers/block/drbd/Makefile | 2 +-
drivers/block/drbd/drbd_buildtag.c | 22 ++++++++++++++++++++++
drivers/block/drbd/drbd_debugfs.c | 2 +-
drivers/block/drbd/drbd_int.h | 1 +
drivers/block/drbd/drbd_main.c | 20 +-------------------
drivers/block/drbd/drbd_proc.c | 2 +-
include/linux/drbd.h | 7 -------
include/linux/drbd_config.h | 16 ++++++++++++++++
include/linux/drbd_genl_api.h | 2 +-
9 files changed, 44 insertions(+), 30 deletions(-)
create mode 100644 drivers/block/drbd/drbd_buildtag.c
create mode 100644 include/linux/drbd_config.h
base-commit: f596da3efaf4130ff61cd029558845808df9bf99
--
2.38.1
next reply other threads:[~2022-12-09 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 14:55 Christoph Böhmwalder [this message]
2022-12-09 14:55 ` [PATCH 1/3] drbd: split off drbd_buildtag into separate file Christoph Böhmwalder
2022-12-09 14:55 ` [PATCH 2/3] drbd: drop API_VERSION define Christoph Böhmwalder
2022-12-09 14:55 ` [PATCH 3/3] drbd: split off drbd_config into separate file Christoph Böhmwalder
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=20221209145504.2273072-1-christoph.boehmwalder@linbit.com \
--to=christoph.boehmwalder@linbit.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).