From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>
Subject: [PATCH] mac80211: add explicit padding in struct ieee80211_tx_info
Date: Wed, 12 Nov 2008 10:05:37 -0500 [thread overview]
Message-ID: <1226502337-11085-1-git-send-email-linville@tuxdriver.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0811120854290.13217@anakin>
Otherwise, the BUILD_BUG_ON calls in ieee80211_tx_info_clear_status can
fail on some architectures.
Signed-off-by: John W. Linville <linville@tuxdriver.com>
---
Why do we have those BUILD_BUG_ON calls anyway? Hmmm...
include/net/mac80211.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/net/mac80211.h b/include/net/mac80211.h
index feb52cc..38302d6 100644
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
@@ -333,6 +333,7 @@ struct ieee80211_tx_info {
u8 antenna_sel_tx;
/* 2 byte hole */
+ u8 pad[2];
union {
struct {
--
1.5.4.3
next parent reply other threads:[~2008-11-12 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0811120854290.13217@anakin>
2008-11-12 15:05 ` John W. Linville [this message]
2008-11-12 17:08 ` [PATCH] mac80211: add explicit padding in struct ieee80211_tx_info Johannes Berg
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=1226502337-11085-1-git-send-email-linville@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=geert@linux-m68k.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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