From: Geoff Levand <geoffrey.levand@am.sony.com>
To: axboe@kernel.dk
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Subject: [patch] block: Minor comment fix
Date: Wed, 3 Sep 2008 15:15:19 -0700 [thread overview]
Message-ID: <48BF0C77.6020901@am.sony.com> (raw)
Minor fix to the inline documentation of blk_release_queue().
Signed-off-by: Geoff Levand <geoffrey.levand@am.sony.com>
---
Hi Jens,
Seems like this comment is in error.
-Geoff
block/blk-sysfs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/block/blk-sysfs.c
+++ b/block/blk-sysfs.c
@@ -245,27 +245,27 @@ queue_attr_store(struct kobject *kobj, s
mutex_lock(&q->sysfs_lock);
if (test_bit(QUEUE_FLAG_DEAD, &q->queue_flags)) {
mutex_unlock(&q->sysfs_lock);
return -ENOENT;
}
res = entry->store(q, page, length);
mutex_unlock(&q->sysfs_lock);
return res;
}
/**
- * blk_cleanup_queue: - release a &struct request_queue when it is no longer needed
+ * blk_release_queue: - release a &struct request_queue when it is no longer needed
* @kobj: the kobj belonging of the request queue to be released
*
* Description:
- * blk_cleanup_queue is the pair to blk_init_queue() or
+ * blk_release_queue is the pair to blk_init_queue() or
* blk_queue_make_request(). It should be called when a request queue is
* being released; typically when a block device is being de-registered.
* Currently, its primary task it to free all the &struct request
* structures that were allocated to the queue and the queue itself.
*
* Caveat:
* Hopefully the low level driver will have finished any
* outstanding requests first...
**/
static void blk_release_queue(struct kobject *kobj)
{
next reply other threads:[~2008-09-03 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 22:15 Geoff Levand [this message]
2008-09-04 6:52 ` [patch] block: Minor comment fix 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=48BF0C77.6020901@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=axboe@kernel.dk \
--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