From: Tracey Dent <tdent48227@gmail.com>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org, Tracey Dent <tdent48227@gmail.com>
Subject: [PATCH 3/3] Staging: speakup: keyhelp: Coding style fix
Date: Fri, 8 Oct 2010 06:13:30 -0400 [thread overview]
Message-ID: <1286532810-5370-3-git-send-email-tdent48227@gmail.com> (raw)
In-Reply-To: <1286532810-5370-1-git-send-email-tdent48227@gmail.com>
Put { on previous line, on line 34. Checkpatch.pl caught this.
---
drivers/staging/speakup/keyhelp.c | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/speakup/keyhelp.c b/drivers/staging/speakup/keyhelp.c
index 81c627c..a74500a 100644
--- a/drivers/staging/speakup/keyhelp.c
+++ b/drivers/staging/speakup/keyhelp.c
@@ -30,11 +30,11 @@ static const int num_key_names = MSG_KEYNAMES_END - MSG_KEYNAMES_START + 1;
static u_short key_offsets[MAXFUNCS], key_data[MAXKEYS];
static u_short masks[] = { 32, 16, 8, 4, 2, 1 };
-static short letter_offsets[26] =
-{ -1, -1, -1, -1, -1, -1, -1, -1,
- -1, -1, -1, -1, -1, -1, -1, -1,
- -1, -1, -1, -1, -1, -1, -1, -1,
- -1, -1 };
+static short letter_offsets[26] = {
+ -1, -1, -1, -1, -1, -1, -1, -1,
+ -1, -1, -1, -1, -1, -1, -1, -1,
+ -1, -1, -1, -1, -1, -1, -1, -1,
+ -1, -1 };
static u_char funcvals[] = {
ATTRIB_BLEEP_DEC, ATTRIB_BLEEP_INC, BLEEPS_DEC, BLEEPS_INC,
--
1.7.3.1.104.gc752e
next prev parent reply other threads:[~2010-10-08 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 10:13 [PATCH 1/3] Staging: speakup: Makefile: Makefile clean up Tracey Dent
2010-10-08 10:13 ` [PATCH 2/3] Staging: speakup: devsynth: file_operations should be const Tracey Dent
2010-10-08 10:13 ` Tracey Dent [this message]
2010-10-08 10:14 [PATCH 1/3] Staging: speakup: Makefile: Makefile clean up Tracey Dent
2010-10-08 10:14 ` [PATCH 3/3] Staging: speakup: keyhelp: Coding style fix Tracey Dent
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=1286532810-5370-3-git-send-email-tdent48227@gmail.com \
--to=tdent48227@gmail.com \
--cc=greg@kroah.com \
--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
all inboxes | Powered by JetHome®