From: Christian Lamparter <chunkeey@googlemail.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
johannes@sipsolutions.net, netdev@vger.kernel.org
Subject: Re: "cfg80211: fix SME connect" breaks iwl3945
Date: Mon, 21 Sep 2009 21:14:06 +0200 [thread overview]
Message-ID: <200909212114.06642.chunkeey@googlemail.com> (raw)
In-Reply-To: <20090921190150.GC23126@kernel.dk>
On Monday 21 September 2009 21:01:50 Jens Axboe wrote:
> Since the latest net pull that contains our above commit
> (bbac31f4c0339f6c51afbd0edfb4959df9b53fa9 in tree), my iwl3945 based x60
> laptop doesn't want to connect to my access point at all. Reverting this
> commit makes it work.
>
> Let me know if you need more info.
Can you try "[PATCH] cfg80211: don't overwrite privacy setting"
from [1]?
[1] http://marc.info/?l=linux-wireless&m=125323296617306&w=2
Regards,
Chr
next prev parent reply other threads:[~2009-09-21 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 19:01 "cfg80211: fix SME connect" breaks iwl3945 Jens Axboe
2009-09-21 19:14 ` Christian Lamparter [this message]
2009-09-21 19:20 ` Jens Axboe
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=200909212114.06642.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=jens.axboe@oracle.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).