From: Chaitanya Kulkarni <kch@nvidia.com>
To: <mst@redhat.com>, <jasowang@redhat.com>, <pbonzini@redhat.com>,
<stefanha@redhat.com>
Cc: <virtualization@lists.linux-foundation.org>,
<linux-block@vger.kernel.org>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: [PATCH 2/4] virtio-blk: don't add a new line
Date: Tue, 19 Apr 2022 21:10:51 -0700 [thread overview]
Message-ID: <20220420041053.7927-3-kch@nvidia.com> (raw)
In-Reply-To: <20220420041053.7927-1-kch@nvidia.com>
Don't split sector assignment line for REQ_OP_READ and REQ_OP_WRITE in
the virtblk_setup_cmd() which fits in one line perfectly.
Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
---
drivers/block/virtio_blk.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
index b77711e73422..d038800474c2 100644
--- a/drivers/block/virtio_blk.c
+++ b/drivers/block/virtio_blk.c
@@ -210,13 +210,11 @@ static blk_status_t virtblk_setup_cmd(struct virtio_device *vdev,
switch (req_op(req)) {
case REQ_OP_READ:
type = VIRTIO_BLK_T_IN;
- vbr->out_hdr.sector = cpu_to_virtio64(vdev,
- blk_rq_pos(req));
+ vbr->out_hdr.sector = cpu_to_virtio64(vdev, blk_rq_pos(req));
break;
case REQ_OP_WRITE:
type = VIRTIO_BLK_T_OUT;
- vbr->out_hdr.sector = cpu_to_virtio64(vdev,
- blk_rq_pos(req));
+ vbr->out_hdr.sector = cpu_to_virtio64(vdev, blk_rq_pos(req));
break;
case REQ_OP_FLUSH:
type = VIRTIO_BLK_T_FLUSH;
--
2.29.0
next prev parent reply other threads:[~2022-04-20 4:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 4:10 [PATCH 0/4] virtio-blk: small cleanup Chaitanya Kulkarni
2022-04-20 4:10 ` [PATCH 1/4] virtio-blk: remove additional check in fast path Chaitanya Kulkarni
2022-04-20 14:54 ` Stefan Hajnoczi
2022-04-20 14:54 ` Stefan Hajnoczi
2022-04-21 21:51 ` Chaitanya Kulkarni
2022-04-20 4:10 ` Chaitanya Kulkarni [this message]
2022-04-20 15:04 ` [PATCH 2/4] virtio-blk: don't add a new line Stefan Hajnoczi
2022-04-20 15:04 ` Stefan Hajnoczi
2022-04-21 21:52 ` Chaitanya Kulkarni
2022-04-20 4:10 ` [PATCH 3/4] virtio-blk: avoid function call in the fast path Chaitanya Kulkarni
2022-04-20 15:16 ` Stefan Hajnoczi
2022-04-20 15:16 ` Stefan Hajnoczi
2022-04-21 21:55 ` Chaitanya Kulkarni
2022-04-20 4:10 ` [PATCH 4/4] virtio-blk: remove deprecated ida_simple_XXX() Chaitanya Kulkarni
2022-04-20 15:19 ` Stefan Hajnoczi
2022-04-20 15:19 ` Stefan Hajnoczi
2022-04-21 21:56 ` [PATCH 0/4] virtio-blk: small cleanup Chaitanya Kulkarni
2022-04-22 14:56 ` Stefan Hajnoczi
2022-04-22 14:56 ` Stefan Hajnoczi
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=20220420041053.7927-3-kch@nvidia.com \
--to=kch@nvidia.com \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.