From: Clayton Casciato <majortomtosourcecontrol@gmail.com>
To: jirislaby@kernel.org
Cc: gregkh@linuxfoundation.org, gustavoars@kernel.org,
linux-kernel@vger.kernel.org,
Clayton Casciato <majortomtosourcecontrol@gmail.com>
Subject: [PATCH] accessibility: braille: braille_console: fix whitespace style issues
Date: Sun, 13 Jun 2021 14:30:32 -0600 [thread overview]
Message-ID: <20210613203031.23721-1-majortomtosourcecontrol@gmail.com> (raw)
Fixed a coding style issue.
Signed-off-by: Clayton Casciato <majortomtosourcecontrol@gmail.com>
---
drivers/accessibility/braille/braille_console.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/accessibility/braille/braille_console.c b/drivers/accessibility/braille/braille_console.c
index 9861302cc7db..a0656c6b595f 100644
--- a/drivers/accessibility/braille/braille_console.c
+++ b/drivers/accessibility/braille/braille_console.c
@@ -225,6 +225,7 @@ static int keyboard_notifier_call(struct notifier_block *blk,
case KBD_POST_KEYSYM:
{
unsigned char type = KTYP(param->value) - 0xf0;
+
if (type == KT_SPEC) {
unsigned char val = KVAL(param->value);
int on_off = -1;
@@ -264,6 +265,7 @@ static int vt_notifier_call(struct notifier_block *blk,
{
struct vt_notifier_param *param = _param;
struct vc_data *vc = param->vc;
+
switch (code) {
case VT_ALLOCATE:
break;
@@ -272,6 +274,7 @@ static int vt_notifier_call(struct notifier_block *blk,
case VT_WRITE:
{
unsigned char c = param->c;
+
if (vc->vc_num != fg_console)
break;
switch (c) {
--
2.31.1
next reply other threads:[~2021-06-13 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 20:30 Clayton Casciato [this message]
2021-06-14 6:01 ` [PATCH] accessibility: braille: braille_console: fix whitespace style issues Jiri Slaby
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=20210613203031.23721-1-majortomtosourcecontrol@gmail.com \
--to=majortomtosourcecontrol@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavoars@kernel.org \
--cc=jirislaby@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).