Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: John W. Linville <linville@tuxdriver.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 00/23] ath9k|ath9k_htc: move dups to common-beacon
Date: Fri, 14 Mar 2014 15:22:13 -0400	[thread overview]
Message-ID: <20140314192212.GD20339@tuxdriver.com> (raw)
In-Reply-To: <531DD589.1090109@rempel-privat.de>

On Mon, Mar 10, 2014 at 04:08:57PM +0100, Oleksij Rempel wrote:
> Am 07.03.2014 11:18, schrieb Sujith Manoharan:
> > Oleksij Rempel wrote:
> >> Last response was about initvals, my patch set affect only beacon code.
> >> Since i don't plan to rewrite ath9k_htc from scratch, i would assume it
> >> will be better to continue this periodic clean work.
> > 
> > I didn't review the patches, but someone else needs to make sure that
> > nothing is broken in ath9k.
> 
> I use this code one week ind STA mode. But if you need more directed
> alternate testing, who is good candidate for this work?

I applied the series and attempted a build.  But...

  CC      drivers/net/wireless/ath/ath9k/tx99.o
In file included from include/linux/bitops.h:33:0,
                 from include/linux/kernel.h:10,
                 from include/linux/skbuff.h:17,
                 from include/linux/if_ether.h:23,
                 from include/linux/etherdevice.h:25,
                 from drivers/net/wireless/ath/ath9k/ath9k.h:20,
                 from drivers/net/wireless/ath/ath9k/tx99.c:17:
drivers/net/wireless/ath/ath9k/tx99.c: In function ?ath9k_tx99_init?:
drivers/net/wireless/ath/ath9k/tx99.c:111:15: error: ?SC_OP_INVALID? undeclared (first use in this function)
  if (test_bit(SC_OP_INVALID, &sc->sc_flags)) {
               ^
/home/linville/git/wireless-next/arch/x86/include/asm/bitops.h:338:25: note: in definition of macro ?test_bit?
  (__builtin_constant_p((nr))  \
                         ^
drivers/net/wireless/ath/ath9k/tx99.c:111:15: note: each undeclared identifier is reported only once for each function it appears in
  if (test_bit(SC_OP_INVALID, &sc->sc_flags)) {
               ^
/home/linville/git/wireless-next/arch/x86/include/asm/bitops.h:338:25: note: in definition of macro ?test_bit?
  (__builtin_constant_p((nr))  \
                         ^
drivers/net/wireless/ath/ath9k/tx99.c:111:33: error: ?struct ath_softc? has no member named ?sc_flags?
  if (test_bit(SC_OP_INVALID, &sc->sc_flags)) {
                                 ^
/home/linville/git/wireless-next/arch/x86/include/asm/bitops.h:339:30: note: in definition of macro ?test_bit?
   ? constant_test_bit((nr), (addr)) \
                              ^
drivers/net/wireless/ath/ath9k/tx99.c:111:33: error: ?struct ath_softc? has no member named ?sc_flags?
  if (test_bit(SC_OP_INVALID, &sc->sc_flags)) {
                                 ^
/home/linville/git/wireless-next/arch/x86/include/asm/bitops.h:340:30: note: in definition of macro ?test_bit?
   : variable_test_bit((nr), (addr)))
                              ^
make[3]: *** [drivers/net/wireless/ath/ath9k/tx99.o] Error 1
make[2]: *** [drivers/net/wireless/ath/ath9k] Error 2
make[1]: *** [drivers/net/wireless/ath] Error 2
make: *** [drivers/net/wireless/] Error 2

I'll be backing this out for now...

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville at tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2014-03-14 19:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1393704966-13985-1-git-send-email-linux@rempel-privat.de>
     [not found] ` <21266.37896.937680.416439@gargle.gargle.HOWL>
2014-03-02  7:27   ` [ath9k-devel] [PATCH 00/23] ath9k|ath9k_htc: move dups to common-beacon Oleksij Rempel
2014-03-02  7:50     ` Sujith Manoharan
2014-03-06 18:42       ` John W. Linville
2014-03-07  9:55         ` Oleksij Rempel
2014-03-07 10:18           ` Sujith Manoharan
2014-03-10 15:08             ` Oleksij Rempel
2014-03-14 19:22               ` John W. Linville [this message]
2014-03-15  7:51                 ` Oleksij Rempel

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=20140314192212.GD20339@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ath9k-devel@lists.ath9k.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