From: Larry Finger <Larry.Finger@lwfinger.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
John Linville <linville@tuxdriver.com>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Problems with WPA in mainline 2.6.31-gitX
Date: Fri, 25 Sep 2009 14:38:31 -0500 [thread overview]
Message-ID: <4ABD1C37.3030102@lwfinger.net> (raw)
In-Reply-To: <200909252042.37881.chunkeey@googlemail.com>
Christian Lamparter wrote:
>
> it made it into 2.6.31-git16:
> "cfg80211: don't overwrite privacy setting"
> 94f85853324e02c3a32bc3101f090dc9a3f512b4
>
> but, "[PATCH] cfg80211: don't set privacy w/o key"
> is still missing.
Thanks, Christian. It turns out I do not need "don't set privacy".
With the latest pull, my system works fine.
Larry
prev parent reply other threads:[~2009-09-25 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 18:25 Problems with WPA in mainline 2.6.31-gitX Larry Finger
2009-09-25 18:42 ` Christian Lamparter
2009-09-25 19:38 ` Larry Finger [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=4ABD1C37.3030102@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=chunkeey@googlemail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).