All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
To: linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, sagi@grimberg.me, hch@lst.de,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
	james.smart@broadcom.com
Subject: [PATCH V2 8/8] nvme-core: add new line after variable declatation
Date: Sun, 28 Feb 2021 18:06:11 -0800	[thread overview]
Message-ID: <20210301020611.18669-9-chaitanya.kulkarni@wdc.com> (raw)
In-Reply-To: <20210301020611.18669-1-chaitanya.kulkarni@wdc.com>

Add a new line in functions nvme_pr_preempt(), nvme_pr_clear(), and
nvme_pr_release() after variable declaration which follows the rest of
the code in the nvme/host/core.c.

No functional change(s) in this patch.

Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
---
 drivers/nvme/host/core.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
index 4858114f4f8a..472fd39a8286 100644
--- a/drivers/nvme/host/core.c
+++ b/drivers/nvme/host/core.c
@@ -2323,18 +2323,21 @@ static int nvme_pr_preempt(struct block_device *bdev, u64 old, u64 new,
 		enum pr_type type, bool abort)
 {
 	u32 cdw10 = nvme_pr_type(type) << 8 | (abort ? 2 : 1);
+
 	return nvme_pr_command(bdev, cdw10, old, new, nvme_cmd_resv_acquire);
 }
 
 static int nvme_pr_clear(struct block_device *bdev, u64 key)
 {
 	u32 cdw10 = 1 | (key ? 1 << 3 : 0);
+
 	return nvme_pr_command(bdev, cdw10, key, 0, nvme_cmd_resv_register);
 }
 
 static int nvme_pr_release(struct block_device *bdev, u64 key, enum pr_type type)
 {
 	u32 cdw10 = nvme_pr_type(type) << 8 | (key ? 1 << 3 : 0);
+
 	return nvme_pr_command(bdev, cdw10, key, 0, nvme_cmd_resv_release);
 }
 
-- 
2.22.1


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  parent reply	other threads:[~2021-03-01  2:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01  2:06 [PATCH V2 0/8] nvme: few cleanups and small improvements Chaitanya Kulkarni
2021-03-01  2:06 ` [PATCH V2 1/8] nvme-core: rename nvme_init_identify() Chaitanya Kulkarni
2021-03-01  2:06 ` [PATCH V2 2/8] nvme-core: split init identify into helper Chaitanya Kulkarni
2021-03-09 10:09   ` Christoph Hellwig
2021-03-01  2:06 ` [PATCH V2 3/8] nvme-core: mark nvme_setup_passsthru() inline Chaitanya Kulkarni
2021-03-01  2:06 ` [PATCH V2 4/8] nvme-core: use likely in nvme_init_request() Chaitanya Kulkarni
2021-03-09 10:07   ` Christoph Hellwig
2021-03-01  2:06 ` [PATCH V2 5/8] nvme-core: don't check nvme_req flags for new req Chaitanya Kulkarni
2021-03-01  2:06 ` [PATCH V2 6/8] nvme-fc: fix the function documentation comment Chaitanya Kulkarni
2021-03-01 19:09   ` James Smart
2021-03-01  2:06 ` [PATCH V2 7/8] nvmet-fc: update function documentation Chaitanya Kulkarni
2021-03-01 19:10   ` James Smart
2021-03-01  2:06 ` Chaitanya Kulkarni [this message]
2021-03-09 10:09 ` [PATCH V2 0/8] nvme: few cleanups and small improvements Christoph Hellwig
2021-03-09 19:42   ` Chaitanya Kulkarni

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=20210301020611.18669-9-chaitanya.kulkarni@wdc.com \
    --to=chaitanya.kulkarni@wdc.com \
    --cc=hch@lst.de \
    --cc=james.smart@broadcom.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.