From: Vadim Kochan <vadim4j@gmail.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Emmanuel Grumbach <egrumbach@gmail.com>,
"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: Wed, 10 Sep 2014 01:07:22 +0300 [thread overview]
Message-ID: <CAMw6YJLeO1JZeY6hNe-TXOS56b-otk+htt5VPPor+9iYCQz53Q@mail.gmail.com> (raw)
In-Reply-To: <540F61D0.9000704@hartkopp.net>
I have the same issue with iwlwifi.
On Tue, Sep 9, 2014 at 11:23 PM, Oliver Hartkopp <socketcan@hartkopp.net> wrote:
> 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-09-09 22:07 UTC|newest]
Thread overview: 14+ 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
[not found] ` <20140909195232.GO29412-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2014-09-09 20:15 ` Oliver Hartkopp
2014-09-09 20:02 ` Emmanuel Grumbach
[not found] ` <CANUX_P3n0v1SzfbYuaAsE4TY7Hz_wo2Fb9SmHVNyFOC9hDhwdg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-09 20:23 ` Oliver Hartkopp
2014-09-09 22:07 ` Vadim Kochan [this message]
[not found] ` <CAMw6YJLeO1JZeY6hNe-TXOS56b-otk+htt5VPPor+9iYCQz53Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-10 5:01 ` Oliver Hartkopp
2014-09-10 8:24 ` Emmanuel Grumbach
[not found] ` <CANUX_P3kOetqEneHgqoCDN4c85SQYD-G=mQj_o1c_TvKmE5psA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-10 9:16 ` Vadim Kochan
[not found] ` <CAMw6YJKgVVnDrn1X7atemC1r9kwvsr3PQDs4qx5KDeeNy-P3VA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=CAMw6YJLeO1JZeY6hNe-TXOS56b-otk+htt5VPPor+9iYCQz53Q@mail.gmail.com \
--to=vadim4j@gmail.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.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).