From: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
To: linux-kernel@vger.kernel.org, marcos.souza.org@gmail.com
Cc: linux-block@vger.kernel.org, axboe@kernel.dk, bvanassche@acm.org,
Chaitanya.Kulkarni@wdc.com
Subject: [PATCH v3 1/3] blk-mq.c: Add documention of function blk_mq_init_queue
Date: Tue, 16 Apr 2019 23:10:28 -0300 [thread overview]
Message-ID: <20190417021030.82998-2-marcos.souza.org@gmail.com> (raw)
In-Reply-To: <20190417021030.82998-1-marcos.souza.org@gmail.com>
Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Signed-off-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
---
block/blk-mq.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/block/blk-mq.c b/block/blk-mq.c
index 9516304a38ee..4a8277a54c03 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -2650,6 +2650,15 @@ void blk_mq_release(struct request_queue *q)
blk_mq_sysfs_deinit(q);
}
+/**
+ * blk_mq_init_queue - Create a new request queue associating a blk_mq_tag_set
+ * @set: tag_set to be associated with the request queue
+ *
+ * Description:
+ * This function creates a new request queue, associating @set with it.
+ *
+ * Returns a new request queue on success, or ERR_PTR() on failure.
+ */
struct request_queue *blk_mq_init_queue(struct blk_mq_tag_set *set)
{
struct request_queue *uninit_q, *q;
--
2.16.4
next prev parent reply other threads:[~2019-04-17 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 2:10 [PATCH v3 0/3] Add documentation of some blk-mq functions Marcos Paulo de Souza
2019-04-17 2:10 ` Marcos Paulo de Souza [this message]
2019-04-17 2:10 ` [PATCH v3 2/3] blk-mq.c: Rework documention of blk_mq_init_sq_queue function Marcos Paulo de Souza
2019-04-17 2:10 ` [PATCH v3 3/3] Documentation: kernel-api.rst: Add block/blk-mq.c Marcos Paulo de Souza
2019-04-24 1:10 ` [PATCH v3 0/3] Add documentation of some blk-mq functions Marcos Paulo de Souza
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=20190417021030.82998-2-marcos.souza.org@gmail.com \
--to=marcos.souza.org@gmail.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.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;
as well as URLs for NNTP newsgroup(s).