From: Christoph Hellwig <hch@infradead.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Pavel Begunkov <asml.silence@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH V2 2/2] block: rename the local variable for holding return value of bio_iov_iter_nvecs
Date: Wed, 9 Dec 2020 08:32:11 +0000 [thread overview]
Message-ID: <20201209083211.GB21031@infradead.org> (raw)
In-Reply-To: <20201203022940.616610-3-ming.lei@redhat.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2020-12-09 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 2:29 [PATCH V2 0/2] block: add bio_iov_iter_nvecs for figuring out nr_vecs Ming Lei
2020-12-03 2:29 ` [PATCH V2 1/2] " Ming Lei
2020-12-03 6:46 ` Hannes Reinecke
2020-12-09 8:31 ` Christoph Hellwig
2020-12-03 2:29 ` [PATCH V2 2/2] block: rename the local variable for holding return value of bio_iov_iter_nvecs Ming Lei
2020-12-03 6:47 ` Hannes Reinecke
2020-12-09 8:32 ` Christoph Hellwig [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=20201209083211.GB21031@infradead.org \
--to=hch@infradead.org \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=willy@infradead.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).