From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH 2/2] nvme-fabrics: Remove unused argument
Date: Sat, 11 May 2019 22:42:55 +0900 [thread overview]
Message-ID: <20190511134255.6790-3-minwoo.im.dev@gmail.com> (raw)
In-Reply-To: <20190511134255.6790-1-minwoo.im.dev@gmail.com>
The variable 'count' is not currently used by nvmf_create_ctrl(), so
remove it.
Signed-off-by: Minwoo Im <minwoo.im.dev at gmail.com>
---
drivers/nvme/host/fabrics.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/nvme/host/fabrics.c b/drivers/nvme/host/fabrics.c
index 592d1e61ef7e..5838f7cd53ac 100644
--- a/drivers/nvme/host/fabrics.c
+++ b/drivers/nvme/host/fabrics.c
@@ -978,7 +978,7 @@ EXPORT_SYMBOL_GPL(nvmf_free_options);
NVMF_OPT_DISABLE_SQFLOW)
static struct nvme_ctrl *
-nvmf_create_ctrl(struct device *dev, const char *buf, size_t count)
+nvmf_create_ctrl(struct device *dev, const char *buf)
{
struct nvmf_ctrl_options *opts;
struct nvmf_transport_ops *ops;
@@ -1073,7 +1073,7 @@ static ssize_t nvmf_dev_write(struct file *file, const char __user *ubuf,
goto out_unlock;
}
- ctrl = nvmf_create_ctrl(nvmf_device, buf, count);
+ ctrl = nvmf_create_ctrl(nvmf_device, buf);
if (IS_ERR(ctrl)) {
ret = PTR_ERR(ctrl);
goto out_unlock;
--
2.17.1
next prev parent reply other threads:[~2019-05-11 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 13:42 [PATCH 0/2] Minor clean-ups for nvme and nvme-fabrics Minwoo Im
2019-05-11 13:42 ` [PATCH 1/2] nvme: Fix typos in nvme status code values Minwoo Im
2019-05-11 19:02 ` Chaitanya Kulkarni
2019-05-12 14:34 ` Sagi Grimberg
2019-05-11 13:42 ` Minwoo Im [this message]
2019-05-11 21:50 ` [PATCH 2/2] nvme-fabrics: Remove unused argument Chaitanya Kulkarni
2019-05-11 22:04 ` Minwoo Im
2019-05-12 15:23 ` Chaitanya Kulkarni
2019-05-12 14:35 ` Sagi Grimberg
2019-05-13 14:01 ` [PATCH 0/2] Minor clean-ups for nvme and nvme-fabrics Christoph Hellwig
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=20190511134255.6790-3-minwoo.im.dev@gmail.com \
--to=minwoo.im.dev@gmail.com \
/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