From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: iwlwifi no authentication with AP - Re: pull request: wireless-next 2014-09-08
Date: Tue, 09 Sep 2014 22:23:44 +0200 [thread overview]
Message-ID: <540F61D0.9000704@hartkopp.net> (raw)
In-Reply-To: <CANUX_P3n0v1SzfbYuaAsE4TY7Hz_wo2Fb9SmHVNyFOC9hDhwdg@mail.gmail.com>
On 09.09.2014 22:02, Emmanuel Grumbach wrote:
> On Tue, Sep 9, 2014 at 10:46 PM, Oliver Hartkopp <socketcan@hartkopp.net> wrote:
>> Hello John, all,
>>
>> on my i7 Laptop with iwlwifi the latest net-next does not connect to my access point:
>
> Are you sure this wasn't the case before?
Indeed I moved to net-next right today - as I also had the LED lockdep splat
on 3.17-rcX with X < 4.
So it can be that this issue was already introduced at the beginning of this
net-next cycle. Don't know, sorry. The latest 3.17-rc4 from Linus' tree works
fine. I'm running a Debian unstable here (in both cases).
> Can you bisect?
Not really. I'm running the kernel on my bare machine - and I just wanted to
go to bed right now ...
So I will be able to test patches tomorrow morning again.
Tnx for your fast feedback,
Oliver
WARNING: multiple messages have this Message-ID (diff)
From: Oliver Hartkopp <socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
To: Emmanuel Grumbach <egrumbach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: "John W. Linville"
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: iwlwifi no authentication with AP - Re: pull request: wireless-next 2014-09-08
Date: Tue, 09 Sep 2014 22:23:44 +0200 [thread overview]
Message-ID: <540F61D0.9000704@hartkopp.net> (raw)
In-Reply-To: <CANUX_P3n0v1SzfbYuaAsE4TY7Hz_wo2Fb9SmHVNyFOC9hDhwdg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 09.09.2014 22:02, Emmanuel Grumbach wrote:
> On Tue, Sep 9, 2014 at 10:46 PM, Oliver Hartkopp <socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org> wrote:
>> Hello John, all,
>>
>> on my i7 Laptop with iwlwifi the latest net-next does not connect to my access point:
>
> Are you sure this wasn't the case before?
Indeed I moved to net-next right today - as I also had the LED lockdep splat
on 3.17-rcX with X < 4.
So it can be that this issue was already introduced at the beginning of this
net-next cycle. Don't know, sorry. The latest 3.17-rc4 from Linus' tree works
fine. I'm running a Debian unstable here (in both cases).
> Can you bisect?
Not really. I'm running the kernel on my bare machine - and I just wanted to
go to bed right now ...
So I will be able to test patches tomorrow morning again.
Tnx for your fast feedback,
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-09 20:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 19:16 pull request: wireless-next 2014-09-08 John W. Linville
2014-09-08 23:44 ` David Miller
2014-09-09 19:46 ` iwlwifi no authentication with AP - " Oliver Hartkopp
2014-09-09 19:52 ` John W. Linville
2014-09-09 20:15 ` Oliver Hartkopp
2014-09-09 20:15 ` Oliver Hartkopp
2014-09-09 20:02 ` Emmanuel Grumbach
2014-09-09 20:23 ` Oliver Hartkopp [this message]
2014-09-09 20:23 ` Oliver Hartkopp
2014-09-09 22:07 ` Vadim Kochan
2014-09-10 5:01 ` Oliver Hartkopp
2014-09-10 5:01 ` Oliver Hartkopp
2014-09-10 8:24 ` Emmanuel Grumbach
2014-09-10 9:16 ` Vadim Kochan
2014-09-10 9:16 ` Vadim Kochan
2014-09-10 9:23 ` Oliver Hartkopp
2014-09-10 9:23 ` Oliver Hartkopp
2014-09-10 16:31 ` Oliver Hartkopp
2014-09-14 18:08 ` Kalle Valo
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=540F61D0.9000704@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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.