From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, "Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: linux-next: wireless tree build failure
Date: Mon, 4 May 2009 22:55:33 -0400 [thread overview]
Message-ID: <20090505025532.GA7917@tuxdriver.com> (raw)
In-Reply-To: <20090505115455.0b147aeb.sfr@canb.auug.org.au>
On Tue, May 05, 2009 at 11:54:55AM +1000, Stephen Rothwell wrote:
> Hi John,
>
> Today's linux-next build (x86_64_allmodconfig) failed like this:
>
> net/mac80211/mlme.c: In function 'ieee80211_enable_ht':
> net/mac80211/mlme.c:126: error: 'IEEE80211_CHAN_NO_HT40PLUS' undeclared (first use in this function)
> net/mac80211/mlme.c:131: error: 'IEEE80211_CHAN_NO_HT40MINUS' undeclared (first use in this function)
>
> Direct cause is commit b3afed6815165a62d20e4487ec2df0d12a2df20d
> ("mac80211: check if HT40+/- is allowed before sending assoc").
>
> I have used the wireless tree from next-20090504 for today.
>
> [You guys build this stuff, right? :-(]
Ooops, sorry! I had to drop a few patches and I didn't get
wireless-next-2.6 pushed back out correctly. It is fixed now.
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next parent reply other threads:[~2009-05-05 3:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090505115455.0b147aeb.sfr@canb.auug.org.au>
2009-05-05 2:55 ` John W. Linville [this message]
2009-11-09 8:08 linux-next: wireless tree build failure Stephen Rothwell
2009-11-09 13:37 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2009-04-22 1:57 Stephen Rothwell
2009-04-22 8:59 ` Johannes Berg
2009-04-22 13:03 ` Stephen Rothwell
2009-04-22 13:06 ` John W. Linville
2009-04-22 13:33 ` Johannes Berg
2009-04-22 13:36 ` Matthew Garrett
2009-06-03 2:52 ` Stephen Rothwell
2009-06-15 12:21 ` Stephen Rothwell
2009-04-22 13:11 ` Johannes Berg
2009-04-28 3:28 ` Stephen Rothwell
2009-04-28 12:50 ` John W. Linville
2009-03-23 4:39 Stephen Rothwell
2009-03-23 4:53 ` David Miller
2009-03-23 5:01 ` Yang Hongyang
2009-03-23 4:55 ` David Miller
2009-03-23 5:06 ` Yang Hongyang
2009-03-23 5:48 ` Stephen Rothwell
2009-03-23 7:59 ` David Miller
2009-03-23 8:10 ` Stephen Rothwell
2009-02-27 2:44 Stephen Rothwell
2009-02-12 8:35 Stephen Rothwell
2009-02-12 16:16 ` John W. Linville
2009-02-12 22:07 ` Stephen Rothwell
2009-02-13 18:24 ` Dave
2009-02-13 18:24 ` 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=20090505025532.GA7917@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-next@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.