From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>,
John Linville <linville@tuxdriver.com>
Subject: Re: Regression since 2.6.31-rc3-wl
Date: Sun, 02 Aug 2009 09:46:54 +0200 [thread overview]
Message-ID: <1249199214.2007.3.camel@johannes.local> (raw)
In-Reply-To: <4A74F1E3.8050502@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
Hi Larry,
On Sat, 2009-08-01 at 20:54 -0500, Larry Finger wrote:
> When I tested 2.6.31-rc4-wl on my old i386 laptop that uses ifup to
> control the network, wireless did not work. The problem was bisected
> to the following:
Thanks for taking the time to bisect the problem, can you be more
specific as to how the problem manifests itself? Are you using ifup to
configure an ad-hoc network?
Thanks,
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-08-02 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 1:54 Regression since 2.6.31-rc3-wl Larry Finger
2009-08-02 7:46 ` Johannes Berg [this message]
2009-08-02 15:33 ` Larry Finger
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=1249199214.2007.3.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).