1. 14 2月, 2014 1 次提交
  2. 05 12月, 2013 1 次提交
  3. 23 8月, 2013 1 次提交
  4. 18 3月, 2013 2 次提交
  5. 12 2月, 2013 1 次提交
  6. 28 11月, 2012 2 次提交
  7. 26 11月, 2012 1 次提交
    • J
      cfg80211: remove remain-on-channel channel type · 42d97a59
      Johannes Berg 提交于
      As mwifiex (and mac80211 in the software case) are the
      only drivers actually implementing remain-on-channel
      with channel type, userspace can't be relying on it.
      This is the case, as it's used only for P2P operations
      right now.
      
      Rather than adding a flag to tell userspace whether or
      not it can actually rely on it, simplify all the code
      by removing the ability to use different channel types.
      Leave only the validation of the attribute, so that if
      we extend it again later (with the needed capability
      flag), it can't break userspace sending invalid data.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      42d97a59
  8. 24 10月, 2012 13 次提交
  9. 09 7月, 2012 1 次提交
    • J
      cfg80211: use wdev in mgmt-tx/ROC APIs · 71bbc994
      Johannes Berg 提交于
      The management frame and remain-on-channel APIs will be
      needed in the P2P device abstraction, so move them over
      to the new wdev-based APIs. Userspace can still use both
      the interface index and wdev identifier for them so it's
      backward compatible, but for the P2P Device wdev it will
      be able to use the wdev identifier only.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      71bbc994
  10. 11 6月, 2012 1 次提交
  11. 29 5月, 2012 1 次提交
  12. 24 5月, 2012 1 次提交
  13. 16 5月, 2012 1 次提交
  14. 11 5月, 2012 1 次提交
  15. 05 5月, 2012 1 次提交
  16. 25 4月, 2012 2 次提交
  17. 23 4月, 2012 1 次提交
  18. 16 4月, 2012 1 次提交
  19. 09 4月, 2012 2 次提交
  20. 26 3月, 2012 1 次提交
  21. 20 3月, 2012 1 次提交
  22. 08 3月, 2012 2 次提交
  23. 07 3月, 2012 1 次提交