From: Sabitha George <sabitha.george@gmail.com>
To: gregkh@linuxfoundation.org, wsa+renesas@sang-engineering.com,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: Sabitha George <sabitha.george@gmail.com>
Subject: [PATCH 1/3] staging:ks7010: use __packed instead of __attribute__((packed))
Date: Sun, 9 Oct 2016 11:22:32 +0530 [thread overview]
Message-ID: <1475992352-8912-1-git-send-email-sabitha.george@gmail.com> (raw)
This patch fixes the below checkpatch warning in ks_hostif.c:
__packed is preferred over __attribute__((packed))
Signed-off-by: Sabitha George <sabitha.george@gmail.com>
---
drivers/staging/ks7010/ks_hostif.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/ks7010/ks_hostif.c b/drivers/staging/ks7010/ks_hostif.c
index c57ca58..b4d422b 100644
--- a/drivers/staging/ks7010/ks_hostif.c
+++ b/drivers/staging/ks7010/ks_hostif.c
@@ -1942,12 +1942,12 @@ void hostif_sme_set_wep(struct ks_wlan_private *priv, int type)
struct wpa_suite_t {
unsigned short size;
unsigned char suite[4][CIPHER_ID_LEN];
-} __attribute__ ((packed));
+} __packed;
struct rsn_mode_t {
uint32_t rsn_mode;
uint16_t rsn_capability;
-} __attribute__ ((packed));
+} __packed;
static
void hostif_sme_set_rsn(struct ks_wlan_private *priv, int type)
@@ -2427,8 +2427,8 @@ void hostif_sme_set_pmksa(struct ks_wlan_private *priv)
struct {
uint8_t bssid[ETH_ALEN];
uint8_t pmkid[IW_PMKID_LEN];
- } __attribute__ ((packed)) list[PMK_LIST_MAX];
- } __attribute__ ((packed)) pmkcache;
+ } __packed list[PMK_LIST_MAX];
+ } __packed pmkcache;
struct pmk_t *pmk;
struct list_head *ptr;
int i;
--
1.9.1
next reply other threads:[~2016-10-09 5:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 5:52 Sabitha George [this message]
2016-10-09 14:50 ` [PATCH 1/3] staging: ks7010: " Greg KH
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=1475992352-8912-1-git-send-email-sabitha.george@gmail.com \
--to=sabitha.george@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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
Powered by JetHome