From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: <linux-block@vger.kernel.org>, <xen-devel@lists.xenproject.org>,
<boris.ostrovsky@oracle.com>, <jgross@suse.com>,
<sstabellini@kernel.org>, <axboe@kernel.dk>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] xen/blkfront: fix comment for need_copy
Date: Mon, 21 Mar 2022 11:05:22 +0100 [thread overview]
Message-ID: <YjhN4neEJMs04JEN@Air-de-Roger> (raw)
In-Reply-To: <20220317220930.5698-1-dongli.zhang@oracle.com>
On Thu, Mar 17, 2022 at 03:09:30PM -0700, Dongli Zhang wrote:
> The 'need_copy' is set when rq_data_dir(req) returns WRITE, in order to
> copy the written data to persistent page.
>
> ".need_copy = rq_data_dir(req) && info->feature_persistent,"
I would also add:
Fixes: c004a6fe0c40 ('block/xen-blkfront: Make it running on 64KB page granularity')
> Signed-off-by: Dongli Zhang <dongli.zhang@oracle.com>
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
Albeit I have one nit since you are already changing the line.
> ---
> drivers/block/xen-blkfront.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
> index 03b5fb341e58..dbc32d0a4b1a 100644
> --- a/drivers/block/xen-blkfront.c
> +++ b/drivers/block/xen-blkfront.c
> @@ -576,7 +576,7 @@ struct setup_rw_req {
> struct blkif_request *ring_req;
> grant_ref_t gref_head;
> unsigned int id;
> - /* Only used when persistent grant is used and it's a read request */
> + /* Only used when persistent grant is used and it's a write request */
While there you might want to adjust the comment to:
"... persistent grants are used ..."
Thanks, Roger.
next prev parent reply other threads:[~2022-03-21 10:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 22:09 [PATCH 1/1] xen/blkfront: fix comment for need_copy Dongli Zhang
2022-03-18 0:27 ` Chaitanya Kulkarni
2022-03-21 10:05 ` Roger Pau Monné [this message]
2022-03-21 10:26 ` Juergen Gross
2022-03-21 12:31 ` 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=YjhN4neEJMs04JEN@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=axboe@kernel.dk \
--cc=boris.ostrovsky@oracle.com \
--cc=dongli.zhang@oracle.com \
--cc=jgross@suse.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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