From: Pranav Athreya <pranavsubbu@gmail.com>
To: Forest Bond <forest@alittletooquiet.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Pranav Athreya <pranavsubbu@gmail.com>
Subject: [PATCH] staging: vt6655: Remove extra blank lines between code blocks
Date: Thu, 11 Jan 2024 12:36:52 +0530 [thread overview]
Message-ID: <20240111070652.71717-1-pranavsubbu@gmail.com> (raw)
Adhere to Linux kernel coding style.
Reported by checkpatch:
drivers/staging/vt6655/rxtx.h:22: CHECK: Please don't use multiple blank lines
drivers/staging/vt6655/vt6655_stage.mod.c:38: CHECK: Please don't use multiple blank lines
^Ignore the blank lines in vt6655_stage.mod.c since *.mod.c files
are included in .gitignore.
Signed-off-by: Pranav Athreya <pranavsubbu@gmail.com>
---
drivers/staging/vt6655/rxtx.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/vt6655/rxtx.h b/drivers/staging/vt6655/rxtx.h
index a67757c9bb5c..be1e5180d57b 100644
--- a/drivers/staging/vt6655/rxtx.h
+++ b/drivers/staging/vt6655/rxtx.h
@@ -19,7 +19,6 @@
#define DEFAULT_MSDU_LIFETIME_RES_64us 8000 /* 64us */
#define DEFAULT_MGN_LIFETIME_RES_64us 125 /* 64us */
-
/*--------------------- Export Definitions -------------------------*/
/*--------------------- Export Variables --------------------------*/
--
2.34.1
next reply other threads:[~2024-01-11 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 7:06 Pranav Athreya [this message]
2024-01-11 7:22 ` [PATCH] staging: vt6655: Remove extra blank lines between code blocks Greg Kroah-Hartman
[not found] ` <CAP1Lp88vEZJtd69Njf9uZ5VXypwZ-5vLdBHf2xoLSpqmeyEQiA@mail.gmail.com>
2024-01-11 9:09 ` Pranav Athreya
2024-01-11 9:27 ` Greg Kroah-Hartman
2024-01-11 10:08 ` Pranav Athreya
2024-01-11 11:08 ` Dan Carpenter
2024-01-11 11:24 ` Pranav Athreya
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=20240111070652.71717-1-pranavsubbu@gmail.com \
--to=pranavsubbu@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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