<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general">
    <title>gmane.linux.kernel.wireless.general</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91327"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91326"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91325"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91324"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91323"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91322"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91320"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91319"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91318"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91317"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91316"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91315"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91314"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91313"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91310"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91309"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91307"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91305"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91304"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91303"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91327">
    <title>Re: [rt2x00-users] rt2x00: missing devices/chips</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91327</link>
    <description>&lt;pre&gt;Hi Xose,

On Tue, May 22, 2012 at 10:35 PM, Xose Vazquez Perez
&amp;lt;xose.vazquez-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

That would indeed be nice, let's see what the future brings.

However, thanks a lot for all your contributions!
Helmut
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Helmut Schaa</dc:creator>
    <dc:date>2012-05-23T11:35:44</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91326">
    <title>[PATCH] ath9k: fix/add bits for spectral scanning</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91326</link>
    <description>&lt;pre&gt;Updates for spectral scanning register modification for AR93x:
 * fix bits for spectral_scan_count
 * add bits for new parameters

Signed-off-by: Zefir Kurtisi &amp;lt;zefir.kurtisi-ASv44eHyqLVBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
---
 drivers/net/wireless/ath/ath9k/ar9003_phy.h |   32 ++++++++++++++++----------
 1 files changed, 20 insertions(+), 12 deletions(-)

diff --git a/drivers/net/wireless/ath/ath9k/ar9003_phy.h b/drivers/net/wireless/ath/ath9k/ar9003_phy.h
index d834d97..44963b0 100644
--- a/drivers/net/wireless/ath/ath9k/ar9003_phy.h
+++ b/drivers/net/wireless/ath/ath9k/ar9003_phy.h
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -817,18 +817,26 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 #define AR_PHY_CHAN_INFO_MEMORY_CAPTURE_MASK         0x0001
 #define AR_PHY_RX_DELAY_DELAY   0x00003FFF
 #define AR_PHY_CCK_TX_CTRL_JAPAN    0x00000010
-#define AR_PHY_SPECTRAL_SCAN_ENABLE         0x00000001
-#define AR_PHY_SPECTRAL_SCAN_ENABLE_S       0
-#define AR_PHY_SPECTRAL_SCAN_ACTIVE         0x00000002
-#define AR_PHY_SPECTRAL_SCAN_ACTIVE_S       1
-#define AR_PHY_SPECTRAL_SCAN_FFT_PERIOD     0x000000F0
-&lt;/pre&gt;</description>
    <dc:creator>Zefir Kurtisi</dc:creator>
    <dc:date>2012-05-23T11:34:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91325">
    <title>Re: [PATCH] rt2800: Initialize max_txpower to MAX_G_TXPOWER and MAX_A_TXPOWER respectively</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91325</link>
    <description>&lt;pre&gt;On Tue, May 22, 2012 at 10:58 PM, Tobias Diedrich
&amp;lt;ranma+openwrt-YxUgxmcw2FPQD6PfKP4TzA&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

It is, but only for devices with correct tx power limit in the eeprom.


So, we can actually drop this patch then?

Helmut
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Helmut Schaa</dc:creator>
    <dc:date>2012-05-23T11:32:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91324">
    <title>Re: [PATCH] mac80211: allow setting default U-APSD queues/max_sp_len for STA</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91324</link>
    <description>&lt;pre&gt;
Well it may be an issue specific to our HW. We didn't want to change
the default behavior of all other mac80211 drivers.

I'm not sure what you mean by "hack" here. We just enable the driver
to override a default value, which is used by mac80211.

Arik
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Arik Nemtsov</dc:creator>
    <dc:date>2012-05-23T11:13:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91323">
    <title>Re: [PATCH] mac80211: allow setting default U-APSD queues/max_sp_len for STA</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91323</link>
    <description>&lt;pre&gt;

Then you could write it down to the commit log instead of forcing others
to ask.


Sounds like a hack to do this in the driver. Why can't mac80211 do it?

&lt;/pre&gt;</description>
    <dc:creator>Kalle Valo</dc:creator>
    <dc:date>2012-05-23T10:59:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91322">
    <title>Re: [PATCH] mac80211: allow setting default U-APSD queues/max_sp_len for STA</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91322</link>
    <description>&lt;pre&gt;
Of course. We want to change this in wlcore. We've encountered
compatibility problems with some APs when we set ACs other than VO to
U-APSD mode.

Arik
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Arik Nemtsov</dc:creator>
    <dc:date>2012-05-23T10:49:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91320">
    <title>Re: [PATCH] mac80211: allow setting default U-APSD queues/max_sp_len for STA</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91320</link>
    <description>&lt;pre&gt;

Why? I assume there is a reason for this...

&lt;/pre&gt;</description>
    <dc:creator>Kalle Valo</dc:creator>
    <dc:date>2012-05-23T10:44:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91319">
    <title>Re: BCM4331 tx failures after S3</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91319</link>
    <description>&lt;pre&gt;
Yikes. I recently did suspend/resume and hibernate testing with BCM43224
(so brcmsmac and bcma), but my system was on AC. I will execute them
again on battery. I want to make sure it is not a BCM4331 specific issue.


When going to S3 the driver is told by mac80211 .stop callback to abort
driver operation so I do not expect b43 has a problem. Instead we
probably have to look at the host PCI code in bcma, but before going
there let me execute my tests.

Can you tell me on what kernel version you see this issue. I would also
like to have a look at your kernel log.



--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Arend van Spriel</dc:creator>
    <dc:date>2012-05-23T09:30:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91318">
    <title>Re: BCM4331 tx failures after S3</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91318</link>
    <description>&lt;pre&gt;
Hi Seth,

as reloading bcma helps could you try the attached patch which runs the
code for pci core initialisation on resume again. I saw some comments
about some functions which should be called on resume for pci core
initialisation in brcmsmac.

The other patch adds some pci workarounds for recent apple devices like
yours.

Both patches are not even compile tested.

Hauke
&lt;/pre&gt;</description>
    <dc:creator>Hauke Mehrtens</dc:creator>
    <dc:date>2012-05-23T09:15:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91317">
    <title>Re: [PATCH] mac80211: add command to get current rssi</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91317</link>
    <description>&lt;pre&gt;
Alternatively we could leave it as general callback "drv_get_rssi()",
add the peer address and let the driver decide if it supports
retrieval of the rssi for the given peer.  Thus, allowing us to do
something like:

if (!local-&amp;gt;ops-&amp;gt;get_rssi) || (drv_get_rssi(local, sdata,
sta-&amp;gt;sta.addr, &amp;amp;sinfo-&amp;gt;signal))
        sinfo-&amp;gt;signal = (s8)sta-&amp;gt;last_signal;

&lt;/pre&gt;</description>
    <dc:creator>Goldenshtein, Victor</dc:creator>
    <dc:date>2012-05-23T08:51:53</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91316">
    <title>[PATCH] mac80211: allow setting default U-APSD queues/max_sp_len for STA</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91316</link>
    <description>&lt;pre&gt;Allow the low level driver to set U-APSD parameters when operating in
managed mode.

Signed-off-by: Arik Nemtsov &amp;lt;arik-Ix1uc/W3ht7QT0dZR+AlfA&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
---
 include/net/mac80211.h |    9 +++++++++
 net/mac80211/main.c    |    8 ++++++++
 net/mac80211/mlme.c    |    4 ++--
 3 files changed, 19 insertions(+), 2 deletions(-)

diff --git a/include/net/mac80211.h b/include/net/mac80211.h
index 4d6e6c6..36c3318 100644
--- a/include/net/mac80211.h
+++ b/include/net/mac80211.h
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1288,6 +1288,13 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; enum ieee80211_hw_flags {
  *
  * &amp;lt; at &amp;gt;offchannel_tx_hw_queue: HW queue ID to use for offchannel TX
  *(if %IEEE80211_HW_QUEUE_CONTROL is set)
+ *
+ * &amp;lt; at &amp;gt;sta_uapsd_queues: Bitmask of enabled U-APSD queues when operating in
+ *managed mode (%IEEE80211_WMM_IE_STA_QOSINFO_AC_VO &amp;amp; co). Defaults
+ *to all four ACs.
+ *
+ * &amp;lt; at &amp;gt;sta_uapsd_max_sp_len: Maximum number of buffered frames AP can deliver in
+ *a service period. Defaults to %IEEE80211_WMM_IE_STA_QOSINFO_SP_ALL
  */
 struct ieee80211_hw {
 struct ieee80211_conf con&lt;/pre&gt;</description>
    <dc:creator>Arik Nemtsov</dc:creator>
    <dc:date>2012-05-23T08:13:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91315">
    <title>Re: [PATCH] ath6kl: Fix missing gpio pin 9 configuration</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91315</link>
    <description>&lt;pre&gt;
No, I didn't. I was just busy with something else, will review soon.

Kalle
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Kalle Valo</dc:creator>
    <dc:date>2012-05-23T07:18:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91314">
    <title>Re: [PATCH] ath6kl: Fix missing gpio pin 9 configuration</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91314</link>
    <description>&lt;pre&gt;

On Tuesday 22 May 2012 12:52 PM, Vasanthakumar Thiagarajan wrote:

I hope you are not dropping this one along with the other
series of two patches sent mistakenly. This is genuine patch.

Vasanth
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Vasanthakumar Thiagarajan</dc:creator>
    <dc:date>2012-05-23T07:16:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91313">
    <title>Re: [PATCH] mac80211: add command to get current rssi</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91313</link>
    <description>&lt;pre&gt;On Tue, May 22, 2012 at 9:40 PM, Johannes Berg
&amp;lt;johannes-cdvu00un1VgdHxzADdlk8Q&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

This is this is for managed only.
I can rename the drv_get_rssi() to drv_get_sta_rssi() and to call it
only for NL80211_IFTYPE_STATION, I think it would clarify things?


&lt;/pre&gt;</description>
    <dc:creator>Goldenshtein, Victor</dc:creator>
    <dc:date>2012-05-23T06:58:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91310">
    <title>wireless-testing in fedora 16</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91310</link>
    <description>&lt;pre&gt;Hi,everybody,I am a beginner in linux and when I compiled the kernel,
"drivers/net/wireless/iwlegacy/common.c    fatal error:iwl-io.h:No such file or 
directory." there is a file named &amp;lt;iwl-io.h&amp;gt; under the fold 
drivers/net/wireless/iwlwifi. I think it is not a problem when these two 
files are in the different folds, right? since there are some other files 
contains the "#include &amp;lt;iwl-io.h&amp;gt;" and they are not in the same directory.

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Xun Ouyang</dc:creator>
    <dc:date>2012-05-23T03:01:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91309">
    <title>Re: [PATCH] rt2800: Initialize max_txpower to MAX_G_TXPOWER and MAX_A_TXPOWER respectively</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91309</link>
    <description>&lt;pre&gt;
Hmm, apparently setting txpower has no effect?
Is it not implemented in the driver?

i.e. regardless of "iw (dev wlan0|phy phy0) set txpower fixed (100|2000)"
I don't see any significant chane in Wifi Analyzer on my Android
phone.

(The real reason I couldn't connect to the AP at all was a different recent
change)

&lt;/pre&gt;</description>
    <dc:creator>Tobias Diedrich</dc:creator>
    <dc:date>2012-05-22T20:58:29</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91307">
    <title>Re: pull request: wireless 2012-05-22</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91307</link>
    <description>&lt;pre&gt;From: "John W. Linville" &amp;lt;linville-2XuSBdqkA4R54TAoqtyWWQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
Date: Tue, 22 May 2012 15:53:48 -0400


Pulled, thanks John.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>David Miller</dc:creator>
    <dc:date>2012-05-22T20:17:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91305">
    <title>[README] Two merges pending...</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91305</link>
    <description>&lt;pre&gt;
After some discussion with John Linville I'm going to let him do
one more wireless merge to me.

I only decided to do this because the changes in his tree were in
his tree before he went away for a week, and therefore have gotten
lots of exposure in -next before the merge window even openned.

Which is more than I can say for some of this shit landing in Linus's
tree the past few days.

Pablo also has a prearranged netfilter merge pending.

DO NOT use this as some sort of sign that if you have some last minute
thing you want merged I can be coaxed into allowing it too.  I very
nearly told John no, and I'm going to tell you no too.

The rest of you stick to bug fixes and maybe a few device ID
additions.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>David Miller</dc:creator>
    <dc:date>2012-05-22T19:28:40</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91304">
    <title>How can I show missing information if interface is in master mode???</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91304</link>
    <description>&lt;pre&gt;Hello

Is there any reason that iwconfig/iw of interfaces which use mac80211 is 
different if interface is in master mode than in managed mode?
The output of an interface in managed mode is like it was in old drivers 
like madwifi i.e. you can see
   bitrate of interface (importent if you want to set it to a lower one 
like for example 24Mbps which most cards have more output than with 54Mbps)
   Channel of interface
   essid of interface
If interface is in master mode you see nothing of that
In fact I have not found how to see essid of an interface in master mode 
and really need that, nor the set bitrate...
iw phy0 info does show the capabilities but not the set values...

Greetings

Beat

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Beat Meier</dc:creator>
    <dc:date>2012-05-22T19:11:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91303">
    <title>Re: [PATCH] rfkill: Add handling when rfkill's type is RFKILL_TYPE_ALL.</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91303</link>
    <description>&lt;pre&gt;
Sorry, I accidentally replied to this in private and then Alex replied
but it all got lost.

He said he was going to change the eeepc use KEY_RFKILL instead of
KEY_WLAN to switch all types...

So I guess what this change really does is make __rfkill_switch_all() be
able to not only switch all devices of a given type, but also be able to
switch all devices of all types.

Alex, can you please rewrite the commit log to make that clearer?

johannes

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Johannes Berg</dc:creator>
    <dc:date>2012-05-22T18:46:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91302">
    <title>Re: [PATCH v1] mac80211: Handle race condition in replay handling</title>
    <link>http://permalink.gmane.org/gmane.linux.kernel.wireless.general/91302</link>
    <description>&lt;pre&gt;

This is still all wrong. If anything, the proper fix should be to leave
the old key around and have the driver somehow indicate which key was
used so the PN comparison can be done against the old key. That would
also solve the problem generically, not just for CCMP in a very hacky
way.

johannes

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Johannes Berg</dc:creator>
    <dc:date>2012-05-22T18:42:51</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.kernel.wireless.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.kernel.wireless.general</link>
  </textinput>
</rdf:RDF>

