All of lore.kernel.org
 help / color / mirror / Atom feed
From: James C Boyd <jcboyd.dev@gmail.com>
To: jkosina@suse.cz
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] HID: hid-input: Fix coding style issue
Date: Wed, 27 May 2015 17:09:08 -0500	[thread overview]
Message-ID: <6ef471e95d8de89ee4cce5182ff4785d0a67fdc4.1432761541.git.jcboyd.dev@gmail.com> (raw)
In-Reply-To: <cover.1432761541.git.jcboyd.dev@gmail.com>
In-Reply-To: <cover.1432761541.git.jcboyd.dev@gmail.com>

This line is too long; split it up.

Signed-off-by: James C Boyd <jcboyd.dev@gmail.com>
---
 drivers/hid/hid-input.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/hid/hid-input.c b/drivers/hid/hid-input.c
index abf4fc6..3511bbab 100644
--- a/drivers/hid/hid-input.c
+++ b/drivers/hid/hid-input.c
@@ -1157,7 +1157,8 @@ void hidinput_hid_event(struct hid_device *hid, struct hid_field *field, struct
 		return;
 
 	/* report the usage code as scancode if the key status has changed */
-	if (usage->type == EV_KEY && (!test_bit(usage->code, input->key)) == value)
+	if (usage->type == EV_KEY &&
+	    (!test_bit(usage->code, input->key)) == value)
 		input_event(input, EV_MSC, MSC_SCAN, usage->hid);
 
 	input_event(input, usage->type, usage->code, value);
-- 

  parent reply	other threads:[~2015-05-27 22:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 22:09 [PATCH 0/3] HID: hid-input: Simplify expression and suppress gcc warning James C Boyd
2015-05-27 22:09 ` [PATCH 1/3] HID: hid-input: Add parentheses to quell " James C Boyd
2015-05-27 22:09 ` [PATCH 2/3] HID: hid-input: Simplify conditional expression James C Boyd
2015-05-27 22:09 ` James C Boyd [this message]
2015-05-28  0:52 ` [PATCH 0/3] HID: hid-input: Simplify expression and suppress gcc warning James C Boyd
2015-05-28  8:44 ` Jiri Kosina

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=6ef471e95d8de89ee4cce5182ff4785d0a67fdc4.1432761541.git.jcboyd.dev@gmail.com \
    --to=jcboyd.dev@gmail.com \
    --cc=jkosina@suse.cz \
    --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 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.