From: Johannes Berg <johannes@sipsolutions.net>
To: Alex Romosan <romosan@sycorax.lbl.gov>
Cc: linux-wireless@vger.kernel.org, ilw@linux.intel.com
Subject: Re: iwlwifi unable to reconnect after suspend since v3.9-rc1
Date: Wed, 27 Mar 2013 18:41:25 +0100 [thread overview]
Message-ID: <1364406085.8388.11.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <87r4j021ac.fsf@sycorax.lbl.gov>
On Wed, 2013-03-27 at 10:35 -0700, Alex Romosan wrote:
> ...i did a bisect using the above and it came up with this:
>
> 89afe614c0c737fd40eda1f8c8ef686246cf3cb6 is the first bad commit
> commit 89afe614c0c737fd40eda1f8c8ef686246cf3cb6
> Author: Johannes Berg <johannes.berg@intel.com>
> Date: Wed Feb 13 15:39:57 2013 +0100
>
> mac80211: fix auth/assoc timeout handling
>
> which makes a lot more sense. i'll try reverting it to see if it fixes
> the problem, or i can try patches if you have any.
Humm, yes, that makes more sense. That commit fixed a bug in another
commit though, I'm surprised you ended up there?! Curious ... I'll check
over the commit and see if I can find anything wrong with it.
johannes
next prev parent reply other threads:[~2013-03-27 17:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 20:52 iwlwifi unable to reconnect after suspend since v3.9-rc1 Alex Romosan
2013-03-27 13:14 ` Johannes Berg
2013-03-27 17:35 ` Alex Romosan
2013-03-27 17:41 ` Johannes Berg [this message]
2013-03-27 18:02 ` Alex Romosan
2013-03-27 19:02 ` Johannes Berg
2013-03-27 19:08 ` Alex Romosan
2013-03-27 19:11 ` Johannes Berg
2013-03-27 19:14 ` Johannes Berg
2013-03-27 19:33 ` Alex Romosan
2013-03-27 19:44 ` Johannes Berg
2013-03-27 20:03 ` Alex Romosan
2013-03-27 20:13 ` Johannes Berg
2013-03-27 20:29 ` Alex Romosan
2013-03-27 17:42 ` Johannes Berg
2013-03-27 17:48 ` Alex Romosan
2013-03-27 17:54 ` Johannes Berg
2013-03-27 18:58 ` Alex Romosan
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=1364406085.8388.11.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=romosan@sycorax.lbl.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.