From: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>, linux-kernel@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>,
"open list:BLOCK LAYER" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] blk-cgroup: Fix doc related to blkcg_exit_queue
Date: Sat, 9 Feb 2019 16:32:50 -0200 [thread overview]
Message-ID: <bb1d8c20-d6c1-535b-fd23-f1f4bd6281ba@gmail.com> (raw)
In-Reply-To: <06802295-4dc7-20bd-a511-99dc37bf8777@acm.org>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
Ping :)
On 1/25/19 1:50 AM, Bart Van Assche wrote:
> On 1/24/19 6:01 PM, Marcos Paulo de Souza wrote:
>> Since 4cf6324b17e9, a portion of function blk_cleanup_queue was moved to
>> a newly created function called blk_exit_queue, including the call of
>> blkcg_exit_queue. So, adjust the documenation according.
>>
>> Signed-off-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
>> ---
>> block/blk-cgroup.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/block/blk-cgroup.c b/block/blk-cgroup.c
>> index 2bed5725aa03..77f37ef8ef06 100644
>> --- a/block/blk-cgroup.c
>> +++ b/block/blk-cgroup.c
>> @@ -1269,7 +1269,7 @@ void blkcg_drain_queue(struct request_queue *q)
>> * blkcg_exit_queue - exit and release blkcg part of request_queue
>> * @q: request_queue being released
>> *
>> - * Called from blk_release_queue(). Responsible for exiting blkcg part.
>> + * Called from blk_exit_queue(). Responsible for exiting blkcg part.
>> */
>> void blkcg_exit_queue(struct request_queue *q)
>> {
>
> Reviewed-by: Bart Van Assche <bvanassche@acm.org>
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1817 bytes --]
next prev parent reply other threads:[~2019-02-09 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 2:01 [PATCH] blk-cgroup: Fix doc related to blkcg_exit_queue Marcos Paulo de Souza
2019-01-25 3:50 ` Bart Van Assche
2019-02-09 18:32 ` Marcos Paulo de Souza [this message]
2019-02-10 15:24 ` 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=bb1d8c20-d6c1-535b-fd23-f1f4bd6281ba@gmail.com \
--to=marcos.souza.org@gmail.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).