From: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
To: Jim Davis <jim.epost@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
<ath9k-devel@lists.ath9k.org>, netdev <netdev@vger.kernel.org>
Subject: Re: [ath9k-devel] randconfig build error with next-20140519, in drivers/net/wireless/ath/ath9k/dfs.c
Date: Wed, 21 May 2014 16:31:45 +0530 [thread overview]
Message-ID: <20140521110143.GA2375@qca.qualcomm.com> (raw)
In-Reply-To: <CA+r1ZhiM7EK08Y4kriXMugMc1Mbj5VDUPwKMq8-_k8Q8qhwPtw@mail.gmail.com>
On Mon, May 19, 2014 at 09:31:16AM -0700, Jim Davis wrote:
> Building with the attached random configuration file,
>
> In file included from drivers/net/wireless/ath/ath9k/eeprom.h:22:0,
> from drivers/net/wireless/ath/ath9k/hw.h:27,
> from drivers/net/wireless/ath/ath9k/dfs.c:18:
> drivers/net/wireless/ath/ath9k/dfs.c: In function ‘ath9k_dfs_process_phyerr’:
> drivers/net/wireless/ath/ath9k/dfs.c:185:14: error: ‘struct ath_softc’
> has no member named ‘debug’
> pe.ts - sc->debug.stats.dfs_stats.last_ts);
> ^
> drivers/net/wireless/ath/ath9k/../ath.h:273:41: note: in definition of
> macro ‘ath_dbg’
> ath_printk(KERN_DEBUG, common, fmt, ##__VA_ARGS__); \
> ^
> drivers/net/wireless/ath/ath9k/dfs.c:186:5: error: ‘struct ath_softc’
> has no member named ‘debug’
> sc->debug.stats.dfs_stats.last_ts = pe.ts;
> ^
> make[5]: *** [drivers/net/wireless/ath/ath9k/dfs.o] Error 1
Please select CONFIG_ATH9K_DEBUGFS.
-Rajkumar
next prev parent reply other threads:[~2014-05-21 11:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 16:31 randconfig build error with next-20140519, in drivers/net/wireless/ath/ath9k/dfs.c Jim Davis
2014-05-21 11:01 ` Rajkumar Manoharan [this message]
2014-05-21 12:12 ` [ath9k-devel] " Julian Calaby
[not found] ` <CAGRGNgXuS-ksFBAtmo8nLAPqPFKo2gHGDCsTcranU-k2-K3rfg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-21 13:55 ` Zefir Kurtisi
2014-05-21 14:38 ` Rajkumar Manoharan
2014-05-21 23:31 ` Julian Calaby
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=20140521110143.GA2375@qca.qualcomm.com \
--to=rmanohar@qti.qualcomm.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=jim.epost@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).