From: Jeff Chua <jeff.chua.linux@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: bugme-daemon@bugzilla.kernel.org,
Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29?
Date: Sat, 28 Feb 2009 07:28:04 +0800 [thread overview]
Message-ID: <b6a2187b0902271528n7bad07c9rf2c56e614780d692@mail.gmail.com> (raw)
In-Reply-To: <b6a2187b0902271524h781300f3kec327de34ab7ccb5@mail.gmail.com>
On Sat, Feb 28, 2009 at 7:24 AM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
>> I just tried it and still doesn't work. May be it's this particular
>> AP, but I tried on another hidden AP and it's not much better.
I just to clarify that this association problem only happens with
"hidden AP". 2.6.28 to 2.6.29-rcX works just fine with non-hidden AP.
Thanks,
Jeff.
next prev parent reply other threads:[~2009-02-27 23:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090224160346.5FF5E10800E@picon.linux-foundation.org>
[not found] ` <200902252339.10129.rjw@sisk.pl>
[not found] ` <b6a2187b0902251738pd7be00ftf415ea6b6bf10329@mail.gmail.com>
2009-02-27 23:24 ` [Bug 12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29? Jeff Chua
2009-02-27 23:28 ` Jeff Chua [this message]
2009-03-14 19:01 2.6.29-rc8: Reported regressions from 2.6.28 Rafael J. Wysocki
2009-03-14 19:01 ` [Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29? Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2009-03-03 19:22 2.6.29-rc6-git7: Reported regressions from 2.6.28 Rafael J. Wysocki
2009-03-03 19:22 ` [Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29? Rafael J. Wysocki
2009-02-23 21:45 2.6.29-rc6: Reported regressions from 2.6.28 Rafael J. Wysocki
2009-02-23 21:45 ` [Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29? Rafael J. Wysocki
2009-02-14 20:35 2.6.29-rc5: Reported regressions from 2.6.28 Rafael J. Wysocki
2009-02-14 20:35 ` [Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29? Rafael J. Wysocki
2009-02-08 19:05 2.6.29-rc4: Reported regressions from 2.6.28 Rafael J. Wysocki
2009-02-08 19:06 ` [Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29? Rafael J. Wysocki
2009-02-04 10:21 2.6.29-rc3-git6: Reported regressions from 2.6.28 Rafael J. Wysocki
2009-02-04 10:23 ` [Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29? Rafael J. Wysocki
2009-02-04 19:15 ` Jeff Chua
2009-02-05 1:37 ` Rafael J. Wysocki
2009-02-05 14:34 ` Jeff Chua
2009-02-14 11:41 ` Jeff Chua
2009-02-14 18:46 ` Jeff Chua
2009-02-14 20:10 ` Rafael J. Wysocki
2009-01-19 21:28 2.6.29-rc2-git1: Reported regressions from 2.6.28 Rafael J. Wysocki
2009-01-19 21:32 ` [Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29? Rafael J. Wysocki
2009-01-11 11:12 2.6.29-rc1: Reported regressions from 2.6.28 Rafael J. Wysocki
2009-01-11 11:16 ` [Bug #12414] iwl4965 cannot use "ap auto" on latest 2.6.28/29? Rafael J. Wysocki
2009-01-11 13:57 ` Jeff Chua
2009-01-11 18:55 ` Rafael J. Wysocki
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=b6a2187b0902271528n7bad07c9rf2c56e614780d692@mail.gmail.com \
--to=jeff.chua.linux@gmail.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rjw@sisk.pl \
/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).