From: Edmundo Carmona Antoranz <eantoranz@gmail.com>
To: gregkh@linuxfoundation.org, kernel-janitors@vger.kernel.org
Cc: Edmundo Carmona Antoranz <eantoranz@gmail.com>
Subject: [PATCH -next 1/3] staging: vt6655: remove unused variable
Date: Sun, 14 Mar 2021 08:59:41 -0600 [thread overview]
Message-ID: <20210314145943.1933245-1-eantoranz@gmail.com> (raw)
Since its introduction in 5449c685a4b3 (Staging: Add pristine
upstream vt6655 driver sources, 2009-04-25), the values
stored in variable byData have never been read in the macro
PCAvDelayByIO. By removing it, we are getting rid of a warning:
drivers/staging/vt6655/upc.h:45:16: warning: variable ‘byData’ set but not used [-Wunused-but-set-variable]
Signed-off-by: Edmundo Carmona Antoranz <eantoranz@gmail.com>
---
drivers/staging/vt6655/upc.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/vt6655/upc.h b/drivers/staging/vt6655/upc.h
index e086ec6e77f7..f00d0fd90003 100644
--- a/drivers/staging/vt6655/upc.h
+++ b/drivers/staging/vt6655/upc.h
@@ -42,14 +42,13 @@
#define PCAvDelayByIO(uDelayUnit) \
do { \
- unsigned char byData; \
unsigned long ii; \
\
if (uDelayUnit <= 50) { \
udelay(uDelayUnit); \
} else { \
for (ii = 0; ii < (uDelayUnit); ii++) \
- byData = inb(0x61); \
+ inb(0x61); \
} \
} while (0)
--
2.30.1
next reply other threads:[~2021-03-14 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 14:59 Edmundo Carmona Antoranz [this message]
2021-03-14 14:59 ` [PATCH -next 2/3] staging: vt6655: correct documentation warnings Edmundo Carmona Antoranz
2021-03-14 14:59 ` [PATCH -next 3/3] staging: vt6655: remove duplicate code Edmundo Carmona Antoranz
2021-03-14 16:01 ` [PATCH -next 1/3] staging: vt6655: remove unused variable Greg KH
2021-03-16 1:46 ` Edmundo Carmona Antoranz
2021-03-16 11:24 ` Greg KH
2021-03-16 11:39 ` Dan Carpenter
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=20210314145943.1933245-1-eantoranz@gmail.com \
--to=eantoranz@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.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 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.