From: reinette chatre <reinette.chatre@intel.com>
To: "sedat.dilek@gmail.com" <sedat.dilek@gmail.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [PATCH 0/2] iwlwifi fixes for 2.6.34
Date: Thu, 13 May 2010 15:15:32 -0700 [thread overview]
Message-ID: <1273788932.7796.376.camel@rchatre-DESK> (raw)
In-Reply-To: <AANLkTilm7VDQkXBMWUeRtH634oq9i9AdUIsv6V3woRH_@mail.gmail.com>
On Thu, 2010-05-13 at 14:54 -0700, Sedat Dilek wrote:
> Whats with "iwl3945: fix scan races"?
hmmm ... cryptic indeed ... I assume you are asking "Why is "iwl3945:
fix scan races" not part of a submission to 2.6.34?
If that is the case then yes, indeed , we did not submit "iwl3945: fix
scan races" to 2.6.34 since the scan races being fixed is between normal
(mac80211 initiated) and internal (as part of rf reset) scans. Like I
mention in the cover letter of the submission that includes that patch
(http://thread.gmane.org/gmane.linux.kernel.wireless.general/50651 ) we
introduce RF reset usage to 3945 through the new "plcp error checking"
patch and thus need the scan races fix for that. Before that patch
nothing in iwl3945 was using RF reset and thus no internal scanning that
could trigger a race.
Reinette
next prev parent reply other threads:[~2010-05-13 22:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 21:49 [PATCH 0/2] iwlwifi fixes for 2.6.34 Reinette Chatre
2010-05-13 21:49 ` [PATCH 1/2] iwlwifi: fix internal scan race Reinette Chatre
2010-05-13 21:49 ` [PATCH 2/2] iwlagn: work around rate scaling reset delay Reinette Chatre
2010-05-13 21:54 ` [PATCH 0/2] iwlwifi fixes for 2.6.34 Sedat Dilek
2010-05-13 22:15 ` reinette chatre [this message]
2010-05-13 22:58 ` Sedat Dilek
2010-05-13 23:16 ` reinette chatre
2010-05-21 18:23 ` John W. Linville
2010-05-21 19:16 ` reinette chatre
-- strict thread matches above, loose matches on Subject: below --
2010-04-16 21:50 Reinette Chatre
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=1273788932.7796.376.camel@rchatre-DESK \
--to=reinette.chatre@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sedat.dilek@gmail.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).