1. 17 12月, 2010 2 次提交
  2. 15 12月, 2010 3 次提交
  3. 14 12月, 2010 25 次提交
  4. 13 12月, 2010 4 次提交
  5. 12 12月, 2010 6 次提交
    • T
      hostap: don't use flush_scheduled_work() · 16359533
      Tejun Heo 提交于
      flush_scheduled_work() is on its way out.  Drop flush_scheduled_work()
      from prism2_free_local_data() and replace it with explicit flushing of
      work items on the respective free functions.  Work items in ap_data
      are flushed from hostap_free_data() and the ones in local_info from
      prism2_free_local_data().
      
      Flush is used instead of cancel as some process and free items from
      queue.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Jes Sorensen <jes@trained-monkey.org>
      Cc: netdev@vger.kernel.org
      16359533
    • T
      i2400m: drop i2400m_schedule_work() · 781ba456
      Tejun Heo 提交于
      i2400m implements dynamic work allocation and queueing mechanism in
      i2400_schedule_work(); however, this is only used for reset and
      recovery which can be served equally well with preallocated per device
      works.
      
      Replace i2400m_schedule_work() with two work structs in struct i2400m.
      These works are explicitly canceled when the device is released making
      calls to flush_scheduled_work(), which is being deprecated,
      unnecessary.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
      Cc: linux-wimax@intel.com
      Cc: netdev@vger.kernel.org
      781ba456
    • T
      sungem: update gp->reset_task flushing · fe8998c5
      Tejun Heo 提交于
      gp->reset_task_pending is always set right before reset_task is
      scheduled and as there is no synchronization between the setting and
      scheduling, busy looping on reset_task_pending before flushing
      reset_task doesn't really buy anything.
      
      Directly flush gp->reset_task on suspend and cancel on detach.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: netdev@vger.kernel.org
      fe8998c5
    • T
      igb[v],ixgbe: don't use flush_scheduled_work() · 760141a5
      Tejun Heo 提交于
      All three drivers use flush_scheduled_work() similarly during driver
      detach.  Replace it with explicit cancels.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: e1000-devel@lists.sourceforge.net
      Cc: netdev@vger.kernel.org
      760141a5
    • T
      iseries_veth: don't use flush_scheduled_work() · 9beb4896
      Tejun Heo 提交于
      flush_scheduled_work() is on its way out.  Remove its usage from
      iseries_veth.
      
      * Cancelling a delayed work, queueing it for immediate execution if
        cancelled and then waiting for completion can be done by simply
        calling flush_delayed_work_sync().
      
      * Explicitly cancel cnx->statemachine_wq on module unload.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Santiago Leon <santil@linux.vnet.ibm.com>
      Cc: netdev@vger.kernel.org
      9beb4896
    • T
      ehea: don't use flush_scheduled_work() · f5c35cc1
      Tejun Heo 提交于
      Directly cancel port->reset_task from ehea_shutdown_single_port()
      instead.  As this cancels the work for each port on driver detach,
      flushing system_wq from ehea_remove() or ehea_module_exit() is no
      longer necessary.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Cc: Breno Leitao <leitao@linux.vnet.ibm.com>
      Cc: netdev@vger.kernel.org
      f5c35cc1