From: "Alina Friedrichsen" <x-alina@gmx.net>
To: kalle.valo@iki.fi, maximlevitsky@gmail.com,
linux-wireless@vger.kernel.org, linville@tuxdriver.com,
Larry.Finger@lwfinger.net
Subject: Re: Regression caused by commit e32b1b9a33759e8a83ac566c4c43f23ed5d6343b
Date: Sat, 24 Jan 2009 00:16:10 +0100 [thread overview]
Message-ID: <20090123231610.50410@gmx.net> (raw)
In-Reply-To: <20090123122921.GA2745@sortiz.org>
Hi Samuel!
> I dont think we should ignore the if_config() return value.
I can write a warning in the kernel log, to help the low-level driver d=
evelopers to debug this problem, but I don't want to stop the new mergi=
ng process, so that the driver hangs in a mostly undefined state.
> Is the 4965 error code sent when trying to set a fixed BSSID in IBSS =
?
> I dont see it in STA mode, when associating to my AP.
I unfortunately don't know the error code, because I don't have the car=
d, but I think if the setting of the BSSID fails here, I should work in=
the new initiated normal joining process, even in broken low-level dri=
vers.
Regards
Alina
--=20
Psssst! Schon vom neuen GMX MultiMessenger geh=F6rt? Der kann`s mit all=
en: http://www.gmx.net/de/go/multimessenger
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-23 23:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 2:08 Regression caused by commit e32b1b9a33759e8a83ac566c4c43f23ed5d6343b Larry Finger
2009-01-23 2:14 ` John W. Linville
2009-01-23 2:21 ` Alina Friedrichsen
2009-01-23 5:32 ` Larry Finger
2009-01-23 7:13 ` Alina Friedrichsen
2009-01-23 9:56 ` Sedat Dilek
2009-01-23 12:29 ` Samuel Ortiz
2009-01-23 23:16 ` Alina Friedrichsen [this message]
2009-01-23 16:33 ` Larry Finger
2009-01-23 20:18 ` Sedat Dilek
2009-01-23 5:17 ` Hin-Tak Leung
2009-01-23 5:40 ` Alina Friedrichsen
2009-01-23 15:47 ` Michael Buesch
2009-01-23 15:49 ` John W. Linville
2009-01-23 16:03 ` Michael Buesch
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=20090123231610.50410@gmx.net \
--to=x-alina@gmx.net \
--cc=Larry.Finger@lwfinger.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=maximlevitsky@gmail.com \
/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).