From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 5/5] staging: wlan-ng: remove unnecessary blank line
Date: Wed, 2 Nov 2016 19:47:49 +0100 [thread overview]
Message-ID: <1478112469-23698-6-git-send-email-sergio.paracuellos@gmail.com> (raw)
In-Reply-To: <1478112469-23698-1-git-send-email-sergio.paracuellos@gmail.com>
Blank lines aren't necessary after an open brace '{'.
Clean them in p80211req.c source file to comply with
the standard kernel coding style.
Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
---
drivers/staging/wlan-ng/p80211req.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/wlan-ng/p80211req.c b/drivers/staging/wlan-ng/p80211req.c
index e9fbe18..c4d8e1b 100644
--- a/drivers/staging/wlan-ng/p80211req.c
+++ b/drivers/staging/wlan-ng/p80211req.c
@@ -171,7 +171,6 @@ static void p80211req_handlemsg(struct wlandevice *wlandev,
struct p80211msg *msg)
{
switch (msg->msgcode) {
-
case DIDmsg_lnxreq_hostwep:{
struct p80211msg_lnxreq_hostwep *req =
(struct p80211msg_lnxreq_hostwep *)msg;
--
1.9.1
prev parent reply other threads:[~2016-11-02 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 18:47 [PATCH 0/5] staging: wlan-ng: Fix several style issues Sergio Paracuellos
2016-11-02 18:47 ` [PATCH 1/5] staging: wlan-ng: add spaces around or operator : HOSTWEP_DEFAULTKEY_MASK Sergio Paracuellos
2016-11-02 18:47 ` [PATCH 2/5] staging: wlan-ng: remove two unnecessary blank lines Sergio Paracuellos
2016-11-02 18:47 ` [PATCH 3/5] staging: wlan-ng: change comparison to NULL to preferred style Sergio Paracuellos
2016-11-02 18:47 ` [PATCH 4/5] staging: wlan-ng: remove unnecessary parentheses Sergio Paracuellos
2016-11-02 18:47 ` Sergio Paracuellos [this message]
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=1478112469-23698-6-git-send-email-sergio.paracuellos@gmail.com \
--to=sergio.paracuellos@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®