From: Madhumitha Prabakaran <madhumithabiw@gmail.com>
To: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Cc: Madhumitha Prabakaran <madhumithabiw@gmail.com>
Subject: [PATCH 2/3] Staging: rtl8723bs: Remove typedef in struct ieee_param
Date: Mon, 15 Apr 2019 15:27:03 -0500 [thread overview]
Message-ID: <6d39bc36c9d73455f9bce46ec3bc9c91d46457d4.1555358247.git.madhumithabiw@gmail.com> (raw)
In-Reply-To: <cover.1555358247.git.madhumithabiw@gmail.com>
In-Reply-To: <cover.1555358247.git.madhumithabiw@gmail.com>
Remove typedef in struct ieee_param, as the struct that
has elements that can reasonably be directly accessed
should never be a typedef.
Signed-off-by: Madhumitha Prabakaran <madhumithabiw@gmail.com>
---
drivers/staging/rtl8723bs/include/ieee80211.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8723bs/include/ieee80211.h b/drivers/staging/rtl8723bs/include/ieee80211.h
index 8077465402c6..1327728e6dff 100644
--- a/drivers/staging/rtl8723bs/include/ieee80211.h
+++ b/drivers/staging/rtl8723bs/include/ieee80211.h
@@ -202,7 +202,7 @@ enum NETWORK_TYPE
#define IsSupportedVHT(NetType) (((NetType) & (WIRELESS_11AC)) ? true : false)
-typedef struct ieee_param {
+struct ieee_param {
u32 cmd;
u8 sta_addr[ETH_ALEN];
union {
@@ -240,7 +240,7 @@ typedef struct ieee_param {
u8 buf[0];
} bcn_ie;
} u;
-}ieee_param;
+};
struct ieee_param_ex {
u32 cmd;
--
2.17.1
next prev parent reply other threads:[~2019-04-15 20:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 20:27 [PATCH 0/3] Cleanups in rtl8723bs Madhumitha Prabakaran
2019-04-15 20:27 ` [PATCH 1/3] Staging: rtl8723bs: Remove typedef in struct ieee_param_ex Madhumitha Prabakaran
2019-04-15 20:27 ` Madhumitha Prabakaran [this message]
2019-04-15 20:27 ` [PATCH 3/3] Staging: rtl8723bs: Remove an unused struct tx_pending_t Madhumitha Prabakaran
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=6d39bc36c9d73455f9bce46ec3bc9c91d46457d4.1555358247.git.madhumithabiw@gmail.com \
--to=madhumithabiw@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®