From: Anders Roxell <anders.roxell@linaro.org>
To: axboe@kernel.dk, maximlevitsky@gmail.com
Cc: linux-kernel@vger.kernel.org, Anders Roxell <anders.roxell@linaro.org>
Subject: [PATCH] memstick: ms_block: fix unused variable warning
Date: Mon, 14 May 2018 12:17:55 +0200 [thread overview]
Message-ID: <20180514101756.2120-1-anders.roxell@linaro.org> (raw)
When building a warning pops up unused variable 'host'
drivers/memstick/core/ms_block.c: In function ‘msb_init_disk’:
drivers/memstick/core/ms_block.c:2097:24: warning: unused variable ‘host’ [-Wunused-variable]
struct memstick_host *host = card->host;
^~~~
Removing the declaration of 'host' in function msb_init_disk.
Fixes: 7c2d748e8476 ("memstick: don't call blk_queue_bounce_limit")
Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
---
drivers/memstick/core/ms_block.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/memstick/core/ms_block.c b/drivers/memstick/core/ms_block.c
index b2d025f42d14..a15181fa45f7 100644
--- a/drivers/memstick/core/ms_block.c
+++ b/drivers/memstick/core/ms_block.c
@@ -2094,7 +2094,6 @@ static const struct block_device_operations msb_bdops = {
static int msb_init_disk(struct memstick_dev *card)
{
struct msb_data *msb = memstick_get_drvdata(card);
- struct memstick_host *host = card->host;
int rc;
unsigned long capacity;
--
2.17.0
next reply other threads:[~2018-05-14 10:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 10:17 Anders Roxell [this message]
2018-05-14 10:17 ` [PATCH] memstick: mspro_block: fix unused variable warning Anders Roxell
2018-05-14 10:52 ` [PATCH v2] " Anders Roxell
2018-05-17 1:40 ` kbuild test robot
2018-05-17 16:32 ` kbuild test robot
2018-05-14 13:17 ` [PATCH] " kbuild test robot
2018-05-14 13:18 ` kbuild test robot
2018-05-14 14:36 ` [PATCH] memstick: ms_block: " 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=20180514101756.2120-1-anders.roxell@linaro.org \
--to=anders.roxell@linaro.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@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