From: Eric Biggers <ebiggers3@gmail.com>
To: linux-block@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>, Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] block: remove outdated part of blkdev_issue_flush() comment
Date: Fri, 24 Mar 2017 14:40:15 -0700 [thread overview]
Message-ID: <20170324214015.GD4986@gmail.com> (raw)
In-Reply-To: <20170123194321.51596-1-ebiggers3@gmail.com>
On Mon, Jan 23, 2017 at 11:43:21AM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> blkdev_issue_flush() is now always synchronous, and it no longer has a
> flags argument. So remove the part of the comment about the WAIT flag.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> block/blk-flush.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/block/blk-flush.c b/block/blk-flush.c
> index 20b7c7a02f1c..3c0ab7361e46 100644
> --- a/block/blk-flush.c
> +++ b/block/blk-flush.c
> @@ -490,8 +490,7 @@ void blk_insert_flush(struct request *rq)
> * Description:
> * Issue a flush for the block device in question. Caller can supply
> * room for storing the error offset in case of a flush error, if they
> - * wish to. If WAIT flag is not passed then caller may check only what
> - * request was pushed in some internal queue for later handling.
> + * wish to.
> */
> int blkdev_issue_flush(struct block_device *bdev, gfp_t gfp_mask,
> sector_t *error_sector)
> --
> 2.11.0.483.g087da7b7c-goog
>
Ping?
prev parent reply other threads:[~2017-03-24 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 19:43 [PATCH] block: remove outdated part of blkdev_issue_flush() comment Eric Biggers
2017-03-24 21:40 ` Eric Biggers [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=20170324214015.GD4986@gmail.com \
--to=ebiggers3@gmail.com \
--cc=axboe@kernel.dk \
--cc=ebiggers@google.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 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).