1. 06 2月, 2016 1 次提交
  2. 29 1月, 2016 2 次提交
  3. 18 11月, 2015 1 次提交
  4. 29 9月, 2015 3 次提交
  5. 21 7月, 2015 6 次提交
  6. 16 6月, 2015 1 次提交
  7. 15 6月, 2015 1 次提交
  8. 26 5月, 2015 2 次提交
  9. 17 3月, 2015 1 次提交
  10. 04 3月, 2015 1 次提交
  11. 03 2月, 2015 1 次提交
  12. 29 1月, 2015 3 次提交
  13. 07 1月, 2015 2 次提交
  14. 26 11月, 2014 1 次提交
  15. 18 11月, 2014 2 次提交
  16. 26 6月, 2014 1 次提交
  17. 23 5月, 2014 1 次提交
  18. 08 5月, 2014 1 次提交
  19. 01 3月, 2014 2 次提交
  20. 13 2月, 2014 2 次提交
  21. 15 10月, 2013 1 次提交
  22. 24 7月, 2013 1 次提交
  23. 20 6月, 2013 2 次提交
  24. 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