From: Mamta Shukla <mamtashukla555@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: forest@alittletooquiet.net, gregkh@linuxfoundation.org
Subject: [PATCH v2 1/3] staging: vt6655: Add blank line after function/struct/union/enum declarations
Date: Sat, 6 Oct 2018 16:56:36 +0530 [thread overview]
Message-ID: <ff2e07eedb4220c53ff681ec6fefb5aa637ae9cb.1538823377.git.mamtashukla555@gmail.com> (raw)
In-Reply-To: <cover.1538823377.git.mamtashukla555@gmail.com>
Add blank line after function/struct/union/enum declarations to fix
checkpatch issue.
CHECK: Please use a blank line after function/struct/union/enum
declarations
Signed-off-by: Mamta Shukla <mamtashukla555@gmail.com>
---
No change in v2.
drivers/staging/vt6655/rxtx.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/vt6655/rxtx.c b/drivers/staging/vt6655/rxtx.c
index 9c4a532..8ae9c68 100644
--- a/drivers/staging/vt6655/rxtx.c
+++ b/drivers/staging/vt6655/rxtx.c
@@ -65,6 +65,7 @@
{RATE_12M, RATE_18M, RATE_24M, RATE_36M, RATE_48M}, /* fallback_rate0 */
{RATE_12M, RATE_12M, RATE_18M, RATE_24M, RATE_36M}, /* fallback_rate1 */
};
+
static const unsigned short wFB_Opt1[2][5] = {
{RATE_12M, RATE_18M, RATE_24M, RATE_24M, RATE_36M}, /* fallback_rate0 */
{RATE_6M, RATE_6M, RATE_12M, RATE_12M, RATE_18M}, /* fallback_rate1 */
--
1.9.1
next prev parent reply other threads:[~2018-10-06 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 11:24 [PATCH v2 0/3] staging: vt6655: Fix coding style issues Mamta Shukla
2018-10-06 11:26 ` Mamta Shukla [this message]
2018-10-06 17:50 ` [Outreachy kernel] [PATCH v2 1/3] staging: vt6655: Add blank line after function/struct/union/enum declarations Himanshu Jha
2018-10-06 11:30 ` [PATCH v2 2/3] staging: vt6655: Add spaces around operators Mamta Shukla
2018-10-06 17:50 ` [Outreachy kernel] " Himanshu Jha
2018-10-06 11:31 ` [PATCH v2 3/3] staging: vt6655: Remove space after cast Mamta Shukla
2018-10-06 17:50 ` [Outreachy kernel] " Himanshu Jha
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=ff2e07eedb4220c53ff681ec6fefb5aa637ae9cb.1538823377.git.mamtashukla555@gmail.com \
--to=mamtashukla555@gmail.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
/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.