From: Larry Finger <Larry.Finger@lwfinger.net>
To: John Linville <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Build error in 2.6.31-rc1-wl
Date: Wed, 01 Jul 2009 15:43:51 -0500 [thread overview]
Message-ID: <4A4BCA87.8020805@lwfinger.net> (raw)
When building the above kernel based on a fress pull of
wireless-testing, I get the following build error:
CC net/core/skbuff.o
net/core/skbuff.c: In function ‘__copy_skb_header’:
net/core/skbuff.c:563: error: ‘struct sk_buff’ has no member named
‘do_not_encrypt’
net/core/skbuff.c:563: error: ‘const struct sk_buff’ has no member
named ‘do_not_encrypt’
make[2]: *** [net/core/skbuff.o] Error 1
The code that errors is
new->vlan_tci = old->vlan_tci;
#if defined(CONFIG_MAC80211) || defined(CONFIG_MAC80211_MODULE)
new->do_not_encrypt = old->do_not_encrypt;
#endif
skb_copy_secmark(new, old);
}
Larry
next reply other threads:[~2009-07-01 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 20:43 Larry Finger [this message]
2009-07-02 12:47 ` Build error in 2.6.31-rc1-wl John W. Linville
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=4A4BCA87.8020805@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).