linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Romosan <romosan@sycorax.lbl.gov>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Guy\, Wey-Yi" <wey-yi.w.guy@intel.com>,
	"linux-wireless\@vger.kernel.org"
	<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] iwlwifi: fix 3945 filter flags
Date: Thu, 19 Aug 2010 09:01:00 -0700	[thread overview]
Message-ID: <87y6c2a8xv.fsf@sycorax.lbl.gov> (raw)
In-Reply-To: <1282037041.3747.2.camel@jlt3.sipsolutions.net> (message from Johannes Berg on Tue, 17 Aug 2010 11:24:01 +0200)

Johannes Berg <johannes@sipsolutions.net> writes:

> From: Johannes Berg <johannes.berg@intel.com>
>
> Applying the filter flags directly as done since
>
> commit 3474ad635db371b0d8d0ee40086f15d223d5b6a4
> Author: Johannes Berg <johannes.berg@intel.com>
> Date:   Thu Apr 29 04:43:05 2010 -0700
>
>     iwlwifi: apply filter flags directly
>
> broke 3945 under some unknown circumstances, as
> reported by Alex.
>
> Since I want to keep the direct application of
> filter flags on iwlagn, duplicate the code into
> both 3945 and agn and remove committing the
> RXON that broke things from the 3945 version.

just to confirm that it works for me. hopefully this will also be
included in the 2.6.36 series. thanks.

--alex--

-- 
| I believe the moment is at hand when, by a paranoiac and active |
|  advance of the mind, it will be possible (simultaneously with  |
|  automatism and other passive states) to systematize confusion  |
|  and thus to help to discredit completely the world of reality. |

      reply	other threads:[~2010-08-19 16:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23 20:14 iwlwifi connection problems Alex Romosan
2010-07-23 20:38 ` Guy, Wey-Yi
2010-07-26  9:17   ` Johannes Berg
2010-07-27  4:59     ` Alex Romosan
2010-07-27  6:37       ` Johannes Berg
2010-08-02  0:18         ` Alex Romosan
2010-08-02 10:58           ` Johannes Berg
2010-08-02 15:42             ` Alex Romosan
2010-08-02 16:23               ` Johannes Berg
2010-08-03  3:53                 ` Alex Romosan
2010-08-03  6:39                   ` Johannes Berg
2010-08-03 12:32                     ` Alex Romosan
2010-08-03 12:43                     ` Alex Romosan
2010-08-04  7:52                       ` Johannes Berg
2010-08-04 14:51                         ` Alex Romosan
2010-08-04 15:03                           ` Johannes Berg
2010-08-04 15:08                             ` Alex Romosan
2010-08-04 15:11                               ` Johannes Berg
2010-08-04 15:12                                 ` Alex Romosan
2010-08-04 15:23                                   ` Johannes Berg
2010-08-16 13:16                                   ` Johannes Berg
2010-08-16 13:44                                     ` Alex Romosan
2010-08-16 16:40                                     ` Alex Romosan
2010-08-16 19:06                                       ` Johannes Berg
2010-08-17  9:24                                       ` [PATCH] iwlwifi: fix 3945 filter flags Johannes Berg
2010-08-19 16:01                                         ` Alex Romosan [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=87y6c2a8xv.fsf@sycorax.lbl.gov \
    --to=romosan@sycorax.lbl.gov \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wey-yi.w.guy@intel.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).