From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: mac80211: fix managed mode BSSID handling
Date: Wed, 20 May 2009 13:06:10 -0400 [thread overview]
Message-ID: <20090520170610.GB7604@tuxdriver.com> (raw)
In-Reply-To: <1242721949.17164.1.camel@johannes.local>
On Tue, May 19, 2009 at 10:32:29AM +0200, Johannes Berg wrote:
> John,
>
> You asked whether the fix-up was correct, but was there also a problem
> applying that to wireless-testing? It seems to be missing a hunk (below)
> in commit
>
> commit 4eca27a55d34bc3256fb367842ab225948fa155b
> Author: Johannes Berg <johannes@sipsolutions.net>
> Date: Thu May 14 13:10:14 2009 +0200
>
> mac80211: fix managed mode BSSID handling
>
> ---
> net/mac80211/main.c | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> --- wireless-testing.orig/net/mac80211/main.c 2009-05-18 19:48:04.000000000 +0200
> +++ wireless-testing/net/mac80211/main.c 2009-05-19 10:30:50.000000000 +0200
> @@ -219,18 +219,26 @@ void ieee80211_bss_info_change_notify(st
> u32 changed)
> {
> struct ieee80211_local *local = sdata->local;
> + static const u8 zero[ETH_ALEN] = { 0 };
Looks like a busted rebase from pending-fixes to master -- that hunk
went to a function that doesn't exist on master.
Thanks for the vigilence! I'll get a fix-up for this...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-05-20 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 8:32 mac80211: fix managed mode BSSID handling Johannes Berg
2009-05-20 17:06 ` John W. Linville [this message]
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=20090520170610.GB7604@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).