From: Khadija Kamran <kkamran.bese16seecs@seecs.edu.pk>
To: outreachy@lists.linux.dev
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Khadija Kamran <kamrankhadijadj@gmail.com>
Subject: [PATCH 2/4] staging: rtl8192e: add blank lines after declarations
Date: Thu, 23 Mar 2023 03:07:02 +0500 [thread overview]
Message-ID: <eae4647540b26afa88ee99209e39f5b461e7132b.1679521517.git.kamrankhadijadj@gmail.com> (raw)
In-Reply-To: <cover.1679521517.git.kamrankhadijadj@gmail.com>
Add blank lines after declarations as reported by checkpatch.pl
"CHECK: Please use a blank line after function/struct/union/enum
declarations"
Signed-off-by: Khadija Kamran <kamrankhadijadj@gmail.com>
---
drivers/staging/rtl8192e/rtllib_rx.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/rtl8192e/rtllib_rx.c b/drivers/staging/rtl8192e/rtllib_rx.c
index c6114d99829b..7144a0630ea6 100644
--- a/drivers/staging/rtl8192e/rtllib_rx.c
+++ b/drivers/staging/rtl8192e/rtllib_rx.c
@@ -231,10 +231,12 @@ rtllib_rx_frame_mgmt(struct rtllib_device *ieee, struct sk_buff *skb,
static unsigned char rfc1042_header[] = {
0xaa, 0xaa, 0x03, 0x00, 0x00, 0x00
};
+
/* Bridge-Tunnel header (for EtherTypes ETH_P_AARP and ETH_P_IPX) */
static unsigned char bridge_tunnel_header[] = {
0xaa, 0xaa, 0x03, 0x00, 0x00, 0xf8
};
+
/* No encapsulation header if EtherType < 0x600 (=length) */
/* Called by rtllib_rx_frame_decrypt */
--
2.34.1
next prev parent reply other threads:[~2023-03-22 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 22:07 [PATCH 0/4] staging: rtl8192e: code cleanup patches Khadija Kamran
2023-03-22 22:07 ` [PATCH 1/4] staging: rtl8192e: remove extra blank lines Khadija Kamran
2023-03-22 22:07 ` Khadija Kamran [this message]
2023-03-22 22:07 ` [PATCH 3/4] staging: rtl8192e: add spaces around binary operators Khadija Kamran
2023-03-22 22:07 ` [PATCH 4/4] staging: rtl8192e: remove blank lines after '{' Khadija Kamran
2023-03-23 5:56 ` [PATCH 0/4] staging: rtl8192e: code cleanup patches Philipp Hortmann
2023-03-23 12:04 ` Khadija Kamran
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=eae4647540b26afa88ee99209e39f5b461e7132b.1679521517.git.kamrankhadijadj@gmail.com \
--to=kkamran.bese16seecs@seecs.edu.pk \
--cc=gregkh@linuxfoundation.org \
--cc=kamrankhadijadj@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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;
as well as URLs for NNTP newsgroup(s).