1. 12 8月, 2014 1 次提交
  2. 04 3月, 2014 1 次提交
  3. 27 12月, 2013 1 次提交
  4. 26 11月, 2013 1 次提交
    • L
      cfg80211: consolidate passive-scan and no-ibss flags · 8fe02e16
      Luis R. Rodriguez 提交于
      These two flags are used for the same purpose, just
      combine them into a no-ir flag to annotate no initiating
      radiation is allowed.
      
      Old userspace sending either flag will have it treated as
      the no-ir flag. To be considerate to older userspace we
      also send both the no-ir flag and the old no-ibss flags.
      Newer userspace will have to be aware of older kernels.
      
      Update all places in the tree using these flags with the
      following semantic patch:
      
      @@
      @@
      -NL80211_RRF_PASSIVE_SCAN
      +NL80211_RRF_NO_IR
      @@
      @@
      -NL80211_RRF_NO_IBSS
      +NL80211_RRF_NO_IR
      @@
      @@
      -IEEE80211_CHAN_PASSIVE_SCAN
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -IEEE80211_CHAN_NO_IBSS
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -NL80211_RRF_NO_IR | NL80211_RRF_NO_IR
      +NL80211_RRF_NO_IR
      @@
      @@
      -IEEE80211_CHAN_NO_IR | IEEE80211_CHAN_NO_IR
      +IEEE80211_CHAN_NO_IR
      @@
      @@
      -(NL80211_RRF_NO_IR)
      +NL80211_RRF_NO_IR
      @@
      @@
      -(IEEE80211_CHAN_NO_IR)
      +IEEE80211_CHAN_NO_IR
      
      Along with some hand-optimisations in documentation, to
      remove duplicates and to fix some indentation.
      Signed-off-by: NLuis R. Rodriguez <mcgrof@do-not-panic.com>
      [do all the driver updates in one go]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      8fe02e16
  5. 03 10月, 2013 1 次提交
  6. 27 9月, 2013 1 次提交
  7. 04 7月, 2013 1 次提交
  8. 25 6月, 2013 1 次提交
  9. 10 2月, 2013 1 次提交
  10. 09 1月, 2013 1 次提交
  11. 07 12月, 2012 2 次提交
  12. 22 11月, 2012 1 次提交
  13. 17 11月, 2012 1 次提交
  14. 16 10月, 2012 1 次提交
  15. 08 9月, 2012 1 次提交
  16. 07 6月, 2012 1 次提交
    • J
      wireless: Remove casts to same type · 2c208890
      Joe Perches 提交于
      Adding casts of objects to the same type is unnecessary
      and confusing for a human reader.
      
      For example, this cast:
      
              int y;
              int *p = (int *)&y;
      
      I used the coccinelle script below to find and remove these
      unnecessary casts.  I manually removed the conversions this
      script produces of casts with __force, __iomem and __user.
      
      @@
      type T;
      T *p;
      @@
      
      -       (T *)p
      +       p
      
      Neatened the mwifiex_deauthenticate_infra function which
      was doing odd things with array pointers and not using
      is_zero_ether_addr.
      Signed-off-by: NJoe Perches <joe@perches.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2c208890
  17. 06 6月, 2012 1 次提交
  18. 09 5月, 2012 2 次提交
    • B
      ipw2200: Fix order of device registration · b4050790
      Ben Hutchings 提交于
      Currently cfg80211 fails to create a "phy80211" symlink in sysfs from
      the net device to the wiphy device.  The latter needs to be registered
      first.
      
      Compile-tested only.
      Reported-by: NCesare Leonardi <celeonar@gmail.com>
      Signed-off-by: NBen Hutchings <ben@decadent.org.uk>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      b4050790
    • S
      net/wireless: ipw2200: Fix WARN_ON occurring in wiphy_register called by ipw_pci_probe · 7ed85b65
      Stanislav Yakovlev 提交于
      The problem was found by Stefan Lippers-Hollmann
      http://marc.info/?l=linux-wireless&m=132720334512946&w=2
      
      WARNING: at /tmp/buildd/linux-aptosid-3.2/debian/build/source_i386_none/net/wireless/core.c:562 wiphy_register+0x45/0x38d [cfg80211]()
      Hardware name: TravelMate 290 \xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff
      Modules linked in: ipw2200(+) iTCO_wdt libipw joydev drm snd_seq snd_timer snd_seq_device iTCO_vendor_support yenta_socket snd intel_agp i2c_i801 pcmcia_rsrc cfg80211 soundcore parport_pc psmouse parport rng_core snd_page_alloc serio_raw pcspkr i2c_algo_bit intel_gtt pcmcia_core evdev irda crc_ccitt rfkill lib80211 processor container ac battery shpchp pci_hotplug button ext4 mbcache jbd2 crc16 dm_mod sd_mod sr_mod crc_t10dif cdrom ata_generic pata_acpi ata_piix libata scsi_mod firewire_ohci firewire_core crc_itu_t 8139too 8139cp mii uhci_hcd ehci_hcd usbcore usb_common [last unloaded: scsi_wait_scan]
      Pid: 328, comm: modprobe Not tainted 3.2-1.slh.4-aptosid-686 #1
      Call Trace:
      [<c012eaf4>] ? warn_slowpath_common+0x7c/0x8f
      [<e0ff0b3e>] ? wiphy_register+0x45/0x38d [cfg80211]
      [<e0ff0b3e>] ? wiphy_register+0x45/0x38d [cfg80211]
      [<c012eb22>] ? warn_slowpath_null+0x1b/0x1f
      [<e0ff0b3e>] ? wiphy_register+0x45/0x38d [cfg80211]
      [<c01f89d7>] ? internal_create_group+0xf5/0xff
      [<e0a2de1c>] ? ipw_pci_probe+0xa9a/0xbd0 [ipw2200]
      [<c01519f4>] ? arch_local_irq_save+0xf/0x14
      [<c0252986>] ? pci_device_probe+0x53/0x9a
      [<c02c2820>] ? driver_probe_device+0x94/0x124
      [<c0252871>] ? pci_match_id+0x15/0x34
      [<c02c28f0>] ? __driver_attach+0x40/0x5b
      [<c02c1d81>] ? bus_for_each_dev+0x37/0x60
      [<c02c25aa>] ? driver_attach+0x17/0x1a
      [<c02c28b0>] ? driver_probe_device+0x124/0x124
      [<c02c22c4>] ? bus_add_driver+0x92/0x1d1
      [<e099d000>] ? 0xe099cfff
      [<c02c2cb8>] ? driver_register+0x7d/0xd4
      [<c017cd50>] ? jump_label_module_notify+0xec/0x167
      [<e099d000>] ? 0xe099cfff
      [<c0253017>] ? __pci_register_driver+0x32/0x87
      [<e099d000>] ? 0xe099cfff
      [<e099d02e>] ? ipw_init+0x2e/0x72 [ipw2200]
      [<c0101173>] ? do_one_initcall+0x7d/0x132
      [<c0145016>] ? __blocking_notifier_call_chain+0x47/0x4f
      [<c0154a73>] ? sys_init_module+0x13a4/0x159c
      [<c03a639f>] ? sysenter_do_call+0x12/0x28
      
      This warning appears only if we apply Ben Hutchings' fix
      http://marc.info/?l=linux-wireless&m=132720195012653&w=2
      for the bug reported by Cesare Leonardi
      http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656813
      with cfg80211 warning during device registration
      ("cfg80211: failed to add phy80211 symlink to netdev!").
      
      We separate device bring up and registration with network stack
      to avoid the problem.
      
      After that Ben Hutchings' fix can be applied to fix the bug.
      
      Cc: stable@kernel.org
      Signed-off-by: NStanislav Yakovlev <stas.yakovlev@gmail.com>
      Tested-by: NStefan Lippers-Hollmann <s.l-h@gmx.de>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      7ed85b65
  19. 24 4月, 2012 1 次提交
  20. 15 4月, 2012 1 次提交
  21. 13 4月, 2012 2 次提交
  22. 07 4月, 2012 1 次提交
  23. 29 3月, 2012 1 次提交
  24. 14 1月, 2012 1 次提交
  25. 18 11月, 2011 1 次提交
  26. 12 11月, 2011 1 次提交
  27. 17 9月, 2011 1 次提交
  28. 18 8月, 2011 1 次提交
  29. 09 8月, 2011 1 次提交
  30. 10 5月, 2011 1 次提交
  31. 31 3月, 2011 1 次提交
  32. 26 1月, 2011 1 次提交
  33. 11 1月, 2011 1 次提交
  34. 06 10月, 2010 1 次提交
  35. 18 8月, 2010 1 次提交
  36. 17 6月, 2010 1 次提交
  37. 03 6月, 2010 1 次提交