All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-block@vger.kernel.org
Cc: kernel-team@fb.com
Subject: [RFC PATCH 3/4] blk-mq: export blk_mq_finish_request()
Date: Fri, 17 Mar 2017 15:03:32 -0700	[thread overview]
Message-ID: <f46a7712d31b003bb52951c10856f2afd063bef2.1489787289.git.osandov@fb.com> (raw)
In-Reply-To: <cover.1489787289.git.osandov@fb.com>
In-Reply-To: <cover.1489787289.git.osandov@fb.com>

From: Omar Sandoval <osandov@fb.com>

This is required for schedulers that define their own put_request().

Signed-off-by: Omar Sandoval <osandov@fb.com>
---
 block/blk-mq.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/block/blk-mq.c b/block/blk-mq.c
index 559f9b0f24a1..94973103e809 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -370,6 +370,7 @@ void blk_mq_finish_request(struct request *rq)
 {
 	blk_mq_finish_hctx_request(blk_mq_map_queue(rq->q, rq->mq_ctx->cpu), rq);
 }
+EXPORT_SYMBOL_GPL(blk_mq_finish_request);
 
 void blk_mq_free_request(struct request *rq)
 {
-- 
2.12.0

  parent reply	other threads:[~2017-03-17 22:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17 22:03 [RFC PATCH 0/4] blk-mq: multiqueue I/O scheduler Omar Sandoval
2017-03-17 22:03 ` [RFC PATCH 1/4] sbitmap: add sbitmap_get_shallow() operation Omar Sandoval
2017-03-17 22:03 ` [RFC PATCH 2/4] blk-mq: add shallow depth option for blk_mq_get_tag() Omar Sandoval
2017-03-17 22:03 ` Omar Sandoval [this message]
2017-03-17 22:03 ` [RFC PATCH 4/4] blk-mq: introduce Kyber multiqueue I/O scheduler Omar Sandoval
2017-03-18  0:55 ` [RFC PATCH 0/4] blk-mq: " Omar Sandoval
2017-03-18 11:14 ` [Lsf] " Hannes Reinecke
2017-03-18 11:15   ` Paolo Valente
2017-03-18 20:18     ` Martin K. Petersen
2017-03-18 15:30   ` Bart Van Assche

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=f46a7712d31b003bb52951c10856f2afd063bef2.1489787289.git.osandov@fb.com \
    --to=osandov@osandov.com \
    --cc=kernel-team@fb.com \
    --cc=linux-block@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 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.