From: Johannes Berg <johannes@sipsolutions.net>
To: Mike McCormack <mikem@ring3k.org>
Cc: netdev@vger.kernel.org
Subject: Re: Wireless fails to associate at boot (regression) due to commit 77fdaa12c
Date: Tue, 21 Jul 2009 12:49:26 +0200 [thread overview]
Message-ID: <1248173366.11316.0.camel@johannes.local> (raw)
In-Reply-To: <392fb48f0907202254t120ff3cmec885d164dc3344d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 453 bytes --]
On Tue, 2009-07-21 at 14:54 +0900, Mike McCormack wrote:
> Hi Johannes,
>
> The following commit causes my wireless network not to associate after
> bootup.
Hard to believe, but you're using wireless-testing which is known to be
broken anyway at this point, because John has been on the road and
hasn't merged fixes...
Also wrong mailing list. If you follow wireless-testing, really do use
(and read maybe) the wireless list.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2009-07-21 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 5:54 Wireless fails to associate at boot (regression) due to commit 77fdaa12c Mike McCormack
2009-07-21 10:49 ` Johannes Berg [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=1248173366.11316.0.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=mikem@ring3k.org \
--cc=netdev@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