From: Jesper Juhl <jesper.juhl@gmail.com>
To: Satyam Sharma <satyam@infradead.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Vojtech Pavlik <vojtech@ucw.cz>,
Johann Deneux <johann.deneux@gmail.com>,
dtor@mail.ru, linux-input@atrey.karlin.mff.cuni.cz,
linux-joystick@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] input: Silence 'unused variable' warning in iforce joystick driver
Date: Fri, 31 Aug 2007 00:50:03 +0200 [thread overview]
Message-ID: <200708310050.03786.jesper.juhl@gmail.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0708310422200.31519@enigma.security.iitk.ac.in>
On 31/08/2007, Satyam Sharma <satyam@infradead.org> wrote:
...
>
> Hmm, would this not still give a warning when JOYSTICK_IFORCE_USB=y?
Arrgh, I messed that one up real good... Thank you for your keen eye Satyam :-)
> [ I didn't know mixing code and declarations (not at top of statement
> block) was accepted style in the kernel ... ]
>
It's not the common case, but this is certainly not the only place in the kernel where we do it.
> IMHO either you should at least wrap that case inside a {} of its
> own (so that the int status; is at top of a statement block), or else,
Yeah, I should...
> preferably, just add "__maybe_unused" to the first declaration that you
> removed just now.
>
Here's an updated patch that actually works as intended.
In the iforce driver we currently get this warning
drivers/input/joystick/iforce/iforce-packets.c: In function 'iforce_get_id_packet':
drivers/input/joystick/iforce/iforce-packets.c:249: warning: unused variable 'status'
if CONFIG_JOYSTICK_IFORCE_USB is not defined.
The warning is easy to avoid by simply moving the variable inside
the only case in the switch that actually use it.
Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
---
diff --git a/drivers/input/joystick/iforce/iforce-packets.c b/drivers/input/joystick/iforce/iforce-packets.c
index 3154ccd..2731057 100644
--- a/drivers/input/joystick/iforce/iforce-packets.c
+++ b/drivers/input/joystick/iforce/iforce-packets.c
@@ -246,13 +246,12 @@ void iforce_process_packet(struct iforce *iforce, u16 cmd, unsigned char *data)
int iforce_get_id_packet(struct iforce *iforce, char *packet)
{
- int status;
-
switch (iforce->bus) {
- case IFORCE_USB:
-
+ case IFORCE_USB: {
#ifdef CONFIG_JOYSTICK_IFORCE_USB
+ int status;
+
iforce->cr.bRequest = packet[0];
iforce->ctrl->dev = iforce->usbdev;
@@ -270,6 +269,7 @@ int iforce_get_id_packet(struct iforce *iforce, char *packet)
usb_unlink_urb(iforce->ctrl);
return -1;
}
+ }
#else
dbg("iforce_get_id_packet: iforce->bus = USB!");
#endif
next prev parent reply other threads:[~2007-08-30 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 22:13 [PATCH] input: Silence 'unused variable' warning in iforce joystick driver Jesper Juhl
2007-08-30 22:57 ` Satyam Sharma
2007-08-30 22:50 ` Jesper Juhl [this message]
2007-08-31 15:26 ` Dmitry Torokhov
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=200708310050.03786.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@mail.ru \
--cc=johann.deneux@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-joystick@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=satyam@infradead.org \
--cc=vojtech@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).