From: Felix Schlepper <f3sch.git@outlook.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
wjsota@gmail.com, Felix Schlepper <f3sch.git@outlook.com>
Subject: [PATCH v2 5/6] Staging: rtl8192e: Remove unnecessary blank line
Date: Thu, 30 Jun 2022 13:30:18 +0200 [thread overview]
Message-ID: <b4fab2e16f35ee09d0c9e1ee1deeb22f4cc98d30.1656587827.git.f3sch.git@outlook.com> (raw)
In-Reply-To: <cover.1656587827.git.f3sch.git@outlook.com>
This addresses an issue raised by checkpatch.pl:
$ ./scripts/checkpatch.pl --terse -f drivers/staging/rtl8192e/rtllib_wx.c
CHECK: Blank lines aren't necessary before a close brace '}'
Signed-off-by: Felix Schlepper <f3sch.git@outlook.com>
---
drivers/staging/rtl8192e/rtllib_wx.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/rtl8192e/rtllib_wx.c b/drivers/staging/rtl8192e/rtllib_wx.c
index 3db29f6eeb89..778b6b7e0939 100644
--- a/drivers/staging/rtl8192e/rtllib_wx.c
+++ b/drivers/staging/rtl8192e/rtllib_wx.c
@@ -599,7 +599,6 @@ int rtllib_wx_set_encode_ext(struct rtllib_device *ieee,
goto done;
}
*crypt = new_crypt;
-
}
if (ext->key_len > 0 && (*crypt)->ops->set_key &&
--
2.36.1
next prev parent reply other threads:[~2022-06-30 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 11:30 [PATCH v2 0/6] Staging: rtl8192e: rtllib_wx codingstyle/refactor Felix Schlepper
2022-06-30 11:30 ` [PATCH v2 1/6] Staging: rtl8192e: Refactored rtllib_modes Felix Schlepper
2022-07-01 7:43 ` Greg KH
2022-06-30 11:30 ` [PATCH v2 2/6] Staging: rtl8192e: Avoid multiple assignments Felix Schlepper
2022-06-30 11:30 ` [PATCH v2 3/6] Staging: rtl8192e: Remove unnecessary parentheses Felix Schlepper
2022-06-30 11:30 ` [PATCH v2 4/6] Staging: rtl8192e: Added braces around else Felix Schlepper
2022-06-30 11:30 ` Felix Schlepper [this message]
2022-06-30 11:30 ` [PATCH v2 6/6] Staging: rtl8192e: Added spaces around '+' Felix Schlepper
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=b4fab2e16f35ee09d0c9e1ee1deeb22f4cc98d30.1656587827.git.f3sch.git@outlook.com \
--to=f3sch.git@outlook.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=wjsota@gmail.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 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®