From: Keerthi Reddy <keerthigd4990@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: outreachy-kernel@googlegroups.com
Subject: [PATCH 2/2] staging: wilc1000: Blank lines aren't necessary before a close brace '}'
Date: Sun, 24 Sep 2017 00:28:12 +0530 [thread overview]
Message-ID: <366b2ad7e1bbc454659e73fda48ec695826ad673.1506192874.git.keerthigd4990@gmail.com> (raw)
In-Reply-To: <cover.1506192874.git.keerthigd4990@gmail.com>
Before closing the brace, the blank line is not needed. That blank
line has not meaning here. so remove it.
Signed-off-by: Keerthi Reddy <keerthigd4990@gmail.com>
---
drivers/staging/wilc1000/wilc_wfi_cfgoperations.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c b/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
index 36dc2a0..e7882b2 100644
--- a/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
+++ b/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
@@ -1111,7 +1111,6 @@ static int del_key(struct wiphy *wiphy, struct net_device *netdev,
g_key_gtk_params.key = NULL;
kfree(g_key_gtk_params.seq);
g_key_gtk_params.seq = NULL;
-
}
if (key_index >= 0 && key_index <= 3) {
--
2.7.4
next prev parent reply other threads:[~2017-09-23 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 18:57 [PATCH 0/2] staging: wilc1000: follow coding guidelines Keerthi Reddy
2017-09-23 18:57 ` [PATCH 1/2] staging: wilc1000: No space is necessary after a cast Keerthi Reddy
2017-09-23 20:03 ` [Outreachy kernel] " Julia Lawall
2017-09-23 18:58 ` Keerthi Reddy [this message]
2017-09-23 20:04 ` [Outreachy kernel] [PATCH 2/2] staging: wilc1000: Blank lines aren't necessary before a close brace '}' Julia Lawall
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=366b2ad7e1bbc454659e73fda48ec695826ad673.1506192874.git.keerthigd4990@gmail.com \
--to=keerthigd4990@gmail.com \
--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.