From: Shailendra Verma <shailendra.capricorn@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Shailendra Verma <shailendra.capricorn@gmail.com>
Subject: [PATCH 8/8] Coding Style Correction.
Date: Sat, 17 Jan 2015 13:28:49 +0530 [thread overview]
Message-ID: <1421481529-19304-1-git-send-email-shailendra.capricorn@gmail.com> (raw)
Signed-off-by: Shailendra Verma <shailendra.capricorn@gmail.com>
---
drivers/input/evdev.c | 30 ++++++++++++++++++++----------
drivers/input/mousedev.c | 18 ++++++++++++------
2 files changed, 32 insertions(+), 16 deletions(-)
diff --git a/drivers/input/evdev.c b/drivers/input/evdev.c
index 18d4b2c..85ee594 100644
--- a/drivers/input/evdev.c
+++ b/drivers/input/evdev.c
@@ -667,16 +667,26 @@ static int handle_eviocgbit(struct input_dev *dev,
switch (type) {
- case 0: bits = dev->evbit; len = EV_MAX; break;
- case EV_KEY: bits = dev->keybit; len = KEY_MAX; break;
- case EV_REL: bits = dev->relbit; len = REL_MAX; break;
- case EV_ABS: bits = dev->absbit; len = ABS_MAX; break;
- case EV_MSC: bits = dev->mscbit; len = MSC_MAX; break;
- case EV_LED: bits = dev->ledbit; len = LED_MAX; break;
- case EV_SND: bits = dev->sndbit; len = SND_MAX; break;
- case EV_FF: bits = dev->ffbit; len = FF_MAX; break;
- case EV_SW: bits = dev->swbit; len = SW_MAX; break;
- default: return -EINVAL;
+ case 0:
+ bits = dev->evbit; len = EV_MAX; break;
+ case EV_KEY:
+ bits = dev->keybit; len = KEY_MAX; break;
+ case EV_REL:
+ bits = dev->relbit; len = REL_MAX; break;
+ case EV_ABS:
+ bits = dev->absbit; len = ABS_MAX; break;
+ case EV_MSC:
+ bits = dev->mscbit; len = MSC_MAX; break;
+ case EV_LED:
+ bits = dev->ledbit; len = LED_MAX; break;
+ case EV_SND:
+ bits = dev->sndbit; len = SND_MAX; break;
+ case EV_FF:
+ bits = dev->ffbit; len = FF_MAX; break;
+ case EV_SW:
+ bits = dev->swbit; len = SW_MAX; break;
+ default:
+ return -EINVAL;
}
return bits_to_user(bits, len, size, p, compat_mode);
diff --git a/drivers/input/mousedev.c b/drivers/input/mousedev.c
index b604564..a9857dd 100644
--- a/drivers/input/mousedev.c
+++ b/drivers/input/mousedev.c
@@ -230,25 +230,31 @@ static void mousedev_key_event(struct mousedev *mousedev,
case BTN_TOUCH:
case BTN_0:
- case BTN_LEFT: index = 0; break;
+ case BTN_LEFT:
+ index = 0; break;
case BTN_STYLUS:
case BTN_1:
- case BTN_RIGHT: index = 1; break;
+ case BTN_RIGHT:
+ index = 1; break;
case BTN_2:
case BTN_FORWARD:
case BTN_STYLUS2:
- case BTN_MIDDLE: index = 2; break;
+ case BTN_MIDDLE:
+ index = 2; break;
case BTN_3:
case BTN_BACK:
- case BTN_SIDE: index = 3; break;
+ case BTN_SIDE:
+ index = 3; break;
case BTN_4:
- case BTN_EXTRA: index = 4; break;
+ case BTN_EXTRA:
+ index = 4; break;
- default: return;
+ default:
+ return;
}
if (value) {
--
1.7.9.5
next reply other threads:[~2015-01-17 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 7:58 Shailendra Verma [this message]
2015-01-17 10:15 ` [PATCH 8/8] Coding Style Correction Jeremiah Mahler
[not found] ` <CA+tKcn_U-5bH8=1MQJXepvz0iXV01xeSCikKJko6XbpFYAk5FA@mail.gmail.com>
2015-01-17 10:58 ` Jeremiah Mahler
[not found] ` <CA+tKcn--30rOiU+aefNAP+LO3+dotADqemLM9-51Mxh150Qzfw@mail.gmail.com>
2015-01-17 11:19 ` Jeremiah Mahler
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=1421481529-19304-1-git-send-email-shailendra.capricorn@gmail.com \
--to=shailendra.capricorn@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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 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).