From: Matthias Kaehlcke <mka@chromium.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Matthias Kaehlcke <mka@chromium.org>
Subject: [PATCH 3/3] cfq-iosched: Delete unused function min_vdisktime()
Date: Fri, 26 May 2017 14:22:37 -0700 [thread overview]
Message-ID: <20170526212237.103525-4-mka@chromium.org> (raw)
In-Reply-To: <20170526212237.103525-1-mka@chromium.org>
This fixes the following warning when building with clang:
block/cfq-iosched.c:970:19: error: unused function 'min_vdisktime'
[-Werror,-Wunused-function]
Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
---
block/cfq-iosched.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index b23c73db4cc0..61cb45553314 100644
--- a/block/cfq-iosched.c
+++ b/block/cfq-iosched.c
@@ -981,15 +981,6 @@ static inline u64 max_vdisktime(u64 min_vdisktime, u64 vdisktime)
return min_vdisktime;
}
-static inline u64 min_vdisktime(u64 min_vdisktime, u64 vdisktime)
-{
- s64 delta = (s64)(vdisktime - min_vdisktime);
- if (delta < 0)
- min_vdisktime = vdisktime;
-
- return min_vdisktime;
-}
-
static void update_min_vdisktime(struct cfq_rb_root *st)
{
struct cfq_group *cfqg;
--
2.13.0.219.gdb65acc882-goog
next prev parent reply other threads:[~2017-05-27 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 21:22 [PATCH 0/3] cfq-iosched: Fix warnings about unused functions Matthias Kaehlcke
2017-05-26 21:22 ` [PATCH 1/3] cfq-iosched: Mark cfq_clear_cfqq_*() as __maybe_unused Matthias Kaehlcke
2017-05-28 7:49 ` Christoph Hellwig
2017-05-30 16:28 ` Doug Anderson
2017-05-26 21:22 ` [PATCH 2/3] cfq-iosched: Fix warning about unused dummy functions Matthias Kaehlcke
2017-05-26 21:22 ` Matthias Kaehlcke [this message]
2017-05-30 15:50 ` [PATCH 3/3] cfq-iosched: Delete unused function min_vdisktime() 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=20170526212237.103525-4-mka@chromium.org \
--to=mka@chromium.org \
--cc=axboe@kernel.dk \
--cc=dianders@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®