From: arjuncr <arjuncr00@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: arjuncr00@gmail.com, linux-kernel@vger.kernel.org
Subject: [PATCH] fix for kernel codig style problems line after variable declarations
Date: Sat, 12 Jun 2021 18:30:17 +0530 [thread overview]
Message-ID: <20210612130017.7955-1-arjuncr00@gmail.com> (raw)
checkpatch.pl detected kernel coding style issues (blank line after variable declarations)
in drivers/accessibility/braille/braille_console.c, so fixed the same by adding the black line
after each variable declaration
Signed-off-by: arjuncr <arjuncr00@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 9861302cc..a0656c6b5 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.25.1
reply other threads:[~2021-06-12 13:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210612130017.7955-1-arjuncr00@gmail.com \
--to=arjuncr00@gmail.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 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.