From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Ming Lei <ming.lei@redhat.com>, Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH] block: Update blk_update_request() documentation
Date: Thu, 3 Jun 2021 14:37:42 -0600 [thread overview]
Message-ID: <0869d606-c473-d004-605f-6d3f4d19ffd9@kernel.dk> (raw)
In-Reply-To: <20210519175226.8853-1-bvanassche@acm.org>
On 5/19/21 11:52 AM, Bart Van Assche wrote:
> Although the original intent was to use blk_update_request() in stacking
> block drivers only, it is used much more widely today. Reflect this in the
> documentation block above this function. See also:
> * commit 32fab448e5e8 ("block: add request update interface").
> * commit 2e60e02297cf ("block: clean up request completion API").
> * commit ed6565e73424 ("block: handle partial completions for special
> payload requests").
Applied, thanks Bart.
--
Jens Axboe
prev parent reply other threads:[~2021-06-03 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 17:52 [PATCH] block: Update blk_update_request() documentation Bart Van Assche
2021-06-03 20:03 ` Bart Van Assche
2021-06-03 20:37 ` Jens Axboe [this message]
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=0869d606-c473-d004-605f-6d3f4d19ffd9@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
/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).