From: Luis Carlos Cobo <luisca@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: 임영빈 <ybim@mmlab.snu.ac.kr>, linux-wireless@vger.kernel.org
Subject: Re: question about open11s installation
Date: Tue, 29 Jul 2008 13:13:34 +0200 [thread overview]
Message-ID: <1217330014.6379.5.camel@localhost> (raw)
In-Reply-To: <1216984564.4758.2.camel@johannes.berg>
On Fri, 2008-07-25 at 13:16 +0200, Johannes Berg wrote:
> > So there's some problem with mesh beaconing with b43 driver.
As it has been noted in a different thread, mesh beaconing in general
was broken by commit "revamp beacon configuration" (1d22d3f6e on
wireless testing). Reverting it will fix it by now and I will send a
patch against wireless-testing head fixing it as soon as possible.
--
Luis Carlos Cobo Rus GnuPG ID: 44019B60
cozybit Inc.
prev parent reply other threads:[~2008-07-29 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 16:05 question about open11s installation 임영빈
2008-07-17 16:55 ` Johannes Berg
2008-07-18 8:51 ` 임영빈
2008-07-25 5:11 ` 임영빈
2008-07-25 5:32 ` YanBo
2008-07-25 11:16 ` Johannes Berg
2008-07-29 11:13 ` Luis Carlos Cobo [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=1217330014.6379.5.camel@localhost \
--to=luisca@cozybit.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ybim@mmlab.snu.ac.kr \
/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).