From: Chaitanya Kulkarni <kch@nvidia.com>
To: <hare@suse.de>, <james.smart@broadcom.com>
Cc: <linux-nvme@lists.infradead.org>, <hch@lst.de>,
<sagi@grimberg.me>, Chaitanya Kulkarni <kch@nvidia.com>
Subject: [PATCH 2/2] nvme-fcloop: no need to return from void function
Date: Fri, 19 May 2023 02:40:52 -0700 [thread overview]
Message-ID: <20230519094052.48575-2-kch@nvidia.com> (raw)
In-Reply-To: <20230519094052.48575-1-kch@nvidia.com>
Remove return at the end of void function.
Signed-off-by: Chaitanya Kulkarni <kch@nvidia.com>
---
drivers/nvme/target/fcloop.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/nvme/target/fcloop.c b/drivers/nvme/target/fcloop.c
index e940a7d37a9d..1ab3d900f2bf 100644
--- a/drivers/nvme/target/fcloop.c
+++ b/drivers/nvme/target/fcloop.c
@@ -645,8 +645,6 @@ fcloop_fcp_recv_work(struct work_struct *work)
}
if (ret)
fcloop_call_host_done(fcpreq, tfcp_req, ret);
-
- return;
}
static void
--
2.40.0
next prev parent reply other threads:[~2023-05-19 9:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230526060759epcas5p3cadfc28c2b45dfc1955cc1bd21f2a351@epcas5p3.samsung.com>
2023-05-19 9:40 ` [PATCH 1/2] nvmet-auth: remove unnecessary break after goto Chaitanya Kulkarni
2023-05-19 9:40 ` Chaitanya Kulkarni [this message]
2023-05-20 5:01 ` [PATCH 2/2] nvme-fcloop: no need to return from void function Christoph Hellwig
2023-05-21 9:56 ` Max Gurtovoy
2023-05-26 6:05 ` Nitesh Shetty
2023-05-20 5:01 ` [PATCH 1/2] nvmet-auth: remove unnecessary break after goto Christoph Hellwig
2023-05-20 8:02 ` Chaitanya Kulkarni
2023-05-25 18:04 ` Keith Busch
2023-05-26 6:04 ` Nitesh Shetty
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=20230519094052.48575-2-kch@nvidia.com \
--to=kch@nvidia.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox