From: gustavo@embeddedor.com (Gustavo A. R. Silva)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] nvmem: lpc18xx_eeprom: fix compile warning
Date: Fri, 5 Oct 2018 09:03:13 +0200 [thread overview]
Message-ID: <20181005070313.GA2217@embeddedor.com> (raw)
Fix the following warning by removing unused variable ret:
drivers/nvmem/lpc18xx_eeprom.c: In function ?lpc18xx_eeprom_remove?:
drivers/nvmem/lpc18xx_eeprom.c:258:6: warning: unused variable ?ret?
[-Wunused-variable]
int ret;
^~~
Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
---
drivers/nvmem/lpc18xx_eeprom.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/nvmem/lpc18xx_eeprom.c b/drivers/nvmem/lpc18xx_eeprom.c
index b42dbad..66cff1e 100644
--- a/drivers/nvmem/lpc18xx_eeprom.c
+++ b/drivers/nvmem/lpc18xx_eeprom.c
@@ -255,7 +255,6 @@ static int lpc18xx_eeprom_probe(struct platform_device *pdev)
static int lpc18xx_eeprom_remove(struct platform_device *pdev)
{
struct lpc18xx_eeprom_dev *eeprom = platform_get_drvdata(pdev);
- int ret;
clk_disable_unprepare(eeprom->clk);
--
2.7.4
next reply other threads:[~2018-10-05 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 7:03 Gustavo A. R. Silva [this message]
2018-10-05 8:06 ` [PATCH] nvmem: lpc18xx_eeprom: fix compile warning Srinivas Kandagatla
2018-10-05 8:12 ` Gustavo A. R. Silva
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=20181005070313.GA2217@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox