From: Michael D Labriola <michael.d.labriola@gmail.com>
To: drbd-dev@lists.linbit.com
Subject: [Drbd-dev] [PATCH 8/8] compat: remove set_bdi_cap_stable_writes
Date: Sun, 13 Dec 2020 00:58:59 -0500 [thread overview]
Message-ID: <20201213055859.3305-9-michael.d.labriola@gmail.com> (raw)
In-Reply-To: <20201213055859.3305-1-michael.d.labriola@gmail.com>
BDI_CAP_STABLE_WRITES goes away in 5.10, resulting in tons of warnings at
compile time. It doesn't look like anything in either drbd or drbd-utils
is using the resulting set_bdi_cap_stable_writes macro anyways, so this
commit removes it.
Signed-off-by: Michael D Labriola <michael.d.labriola@gmail.com>
---
drbd/drbd-kernel-compat/drbd_wrappers.h | 7 -------
1 file changed, 7 deletions(-)
diff --git a/drbd/drbd-kernel-compat/drbd_wrappers.h b/drbd/drbd-kernel-compat/drbd_wrappers.h
index c0d8981c..01fdbf22 100644
--- a/drbd/drbd-kernel-compat/drbd_wrappers.h
+++ b/drbd/drbd-kernel-compat/drbd_wrappers.h
@@ -127,13 +127,6 @@ static inline void blk_queue_write_cache(struct request_queue *q, bool enabled,
#define KREF_INIT(N) { ATOMIC_INIT(N) }
#endif
-#ifdef BDI_CAP_STABLE_WRITES /* >= v3.9 */
-#define set_bdi_cap_stable_writes(cap) do { (cap) |= BDI_CAP_STABLE_WRITES; } while (0)
-#else /* < v3.9 */
-#warning "BDI_CAP_STABLE_WRITES not available"
-#define set_bdi_cap_stable_writes(cap) do { } while (0)
-#endif
-
#ifdef COMPAT_HAVE_POINTER_BACKING_DEV_INFO /* >= v4.11 */
#define bdi_from_device(device) (device->ldev->backing_bdev->bd_disk->queue->backing_dev_info)
#else /* < v4.11 */
--
2.17.1
next prev parent reply other threads:[~2020-12-13 5:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 5:58 [Drbd-dev] Get drbd-9.0 branch building with Linux 5.9 and 5.10 Michael D Labriola
2020-12-13 5:58 ` [Drbd-dev] [PATCH 1/8] compat: fix include for submit_bio test Michael D Labriola
2020-12-13 5:58 ` [Drbd-dev] [PATCH 2/8] compat: fix include for blkdev_get_by_path test Michael D Labriola
2020-12-13 5:58 ` [Drbd-dev] [PATCH 3/8] drbd: don't include vermagic.h Michael D Labriola
2020-12-13 5:58 ` [Drbd-dev] [PATCH 4/8] drbd: fix drbd_submit_bio argument handling Michael D Labriola
2020-12-13 5:58 ` [Drbd-dev] [PATCH 5/8] drbd: use sock_set_keepalive() instead of kernel_setsockopt() Michael D Labriola
2020-12-13 5:58 ` [Drbd-dev] [PATCH 6/8] drbd: get rid of set_fs() usage Michael D Labriola
2020-12-13 5:58 ` [Drbd-dev] [PATCH 7/8] drbd: don't use sched_setscheduler() Michael D Labriola
2020-12-13 5:58 ` Michael D Labriola [this message]
2020-12-14 10:18 ` [Drbd-dev] Get drbd-9.0 branch building with Linux 5.9 and 5.10 Christoph Böhmwalder
2020-12-14 15:35 ` Michael Labriola
-- strict thread matches above, loose matches on Subject: below --
2020-12-13 5:06 Michael D Labriola
2020-12-13 5:07 ` [Drbd-dev] [PATCH 8/8] compat: remove set_bdi_cap_stable_writes Michael D Labriola
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=20201213055859.3305-9-michael.d.labriola@gmail.com \
--to=michael.d.labriola@gmail.com \
--cc=drbd-dev@lists.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