From: "John W. Linville" <linville@tuxdriver.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Alina Friedrichsen <x-alina@gmx.net>,
samuel@sortiz.org, Kalle Valo <kalle.valo@iki.fi>,
maximlevitsky@gmail.com,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Regression caused by commit e32b1b9a33759e8a83ac566c4c43f23ed5d6343b
Date: Thu, 22 Jan 2009 21:14:14 -0500 [thread overview]
Message-ID: <20090123021413.GB3177@tuxdriver.com> (raw)
In-Reply-To: <4979269F.1060500@lwfinger.net>
On Thu, Jan 22, 2009 at 08:08:31PM -0600, Larry Finger wrote:
> With the commit of the subject, my b43 and p54usb devices stopped working. They could
> associate and authenticate with my WPA2 network, but never finish the DHCP connection and
> get an IP address. Surprisingly, my rtl8187 devices continued to work.
>
> Please excuse the second sending of this. I missed wireless the first time.
I reverted this in wireless-testing (and it never went anywhere
upstream). Of course, now it looks like Samuel has a fix...maybe
I'll combine them...
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2009-01-23 2:12 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 [this message]
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
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=20090123021413.GB3177@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=samuel@sortiz.org \
--cc=x-alina@gmx.net \
/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).