From: bugzilla-daemon@bugzilla.kernel.org
To: backports@vger.kernel.org
Subject: [Bug 51751] New: debug build of ath9k fails.
Date: Sun, 16 Dec 2012 22:21:05 +0000 (UTC) [thread overview]
Message-ID: <bug-51751-58281@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=51751
Summary: debug build of ath9k fails.
Product: Backports project
Version: unspecified
Kernel Version: 3.6.9 - 3.6.10
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Not sure
AssignedTo: backports@vger.kernel.org
ReportedBy: arclanceSignup@gmail.com
Regression: Yes
Since 2012-12-04 building the ath9k module from compat-wireless fails when
these build options are enabled.
export CONFIG_ATH9K_DEBUGFS=y
export CONFIG_ATH_DEBUG=y
This is the error message from a failed build.
CC [M]
/media/Linux_Data/Programs_CB10/compat_wireless/compat-wireless-2012-12-15-p/compat-wireless-2012-12-15-p/drivers/net/wireless/ath/ath9k/debug.o
/media/Linux_Data/Programs_CB10/compat_wireless/compat-wireless-2012-12-15-p/compat-wireless-2012-12-15-p/drivers/net/wireless/ath/ath9k/debug.c:
In function ‘ath9k_sta_add_debugfs’:
/media/Linux_Data/Programs_CB10/compat_wireless/compat-wireless-2012-12-15-p/compat-wireless-2012-12-15-p/drivers/net/wireless/ath/ath9k/debug.c:1589:4:
error: ‘struct ath_node’ has no member named ‘node_stat’
/media/Linux_Data/Programs_CB10/compat_wireless/compat-wireless-2012-12-15-p/compat-wireless-2012-12-15-p/drivers/net/wireless/ath/ath9k/debug.c:
In function ‘ath9k_sta_remove_debugfs’:
/media/Linux_Data/Programs_CB10/compat_wireless/compat-wireless-2012-12-15-p/compat-wireless-2012-12-15-p/drivers/net/wireless/ath/ath9k/debug.c:1599:19:
error: ‘struct ath_node’ has no member named ‘node_stat’
make[5]: ***
[/media/Linux_Data/Programs_CB10/compat_wireless/compat-wireless-2012-12-15-p/compat-wireless-2012-12-15-p/drivers/net/wireless/ath/ath9k/debug.o]
Error 1
make[4]: ***
[/media/Linux_Data/Programs_CB10/compat_wireless/compat-wireless-2012-12-15-p/compat-wireless-2012-12-15-p/drivers/net/wireless/ath/ath9k]
Error 2
make[3]: ***
[/media/Linux_Data/Programs_CB10/compat_wireless/compat-wireless-2012-12-15-p/compat-wireless-2012-12-15-p/drivers/net/wireless/ath]
Error 2
make[2]: ***
[/media/Linux_Data/Programs_CB10/compat_wireless/compat-wireless-2012-12-15-p/compat-wireless-2012-12-15-p/drivers/net/wireless]
Error 2
make[1]: ***
[_module_/media/Linux_Data/Programs_CB10/compat_wireless/compat-wireless-2012-12-15-p/compat-wireless-2012-12-15-p]
Error 2
make[1]: Leaving directory
`/usr/src/linux-headers-3.6.0-10.dmz.1-liquorix-amd64'
make: *** [modules] Error 2
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-12-16 22:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 22:21 bugzilla-daemon [this message]
2012-12-25 10:26 ` [Bug 51751] debug build of ath9k fails bugzilla-daemon
2012-12-25 14:51 ` bugzilla-daemon
2012-12-25 14:55 ` bugzilla-daemon
2012-12-25 15:39 ` bugzilla-daemon
2012-12-25 16:47 ` bugzilla-daemon
2012-12-26 2:07 ` bugzilla-daemon
2013-06-03 2:34 ` bugzilla-daemon
2013-07-30 14:10 ` bugzilla-daemon
2013-11-24 19:24 ` bugzilla-daemon
2013-11-24 19:24 ` bugzilla-daemon
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=bug-51751-58281@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=backports@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;
as well as URLs for NNTP newsgroup(s).