Skip to content

K
Kernel

openeuler / Kernel
接近 2 年 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 20 6月, 2014 2 次提交
  3. 23 5月, 2014 1 次提交
  5. 23 4月, 2014 2 次提交
  7. 09 4月, 2014 1 次提交
  9. 14 3月, 2014 1 次提交
  11. 07 3月, 2014 1 次提交
    • T
      wireless/rt2x00: don't use PREPARE_WORK in rt2800usb.c · d82fead4
      由 Tejun Heo 提交于 
      PREPARE_[DELAYED_]WORK() are being phased out.  They have few users
and a nasty surprise in terms of reentrancy guarantee as workqueue
considers work items to be different if they don't have the same work
function.

Update rt2800usb.c to use INIT_WORK() instead of PREPARE_WORK().  As
the work item isn't in active use during rt2800usb_probe_hw(), this
doesn't cause any behavior difference.

It would probably be best to route this with other related updates
through the workqueue tree.

Only compile tested.
Signed-off-by: NTejun Heo <tj@kernel.org>
Cc: Ivo van Doorn <IvDoorn@gmail.com>
Cc: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless@vger.kernel.org
      d82fead4
  13. 04 3月, 2014 1 次提交
  15. 25 2月, 2014 1 次提交
    • T
      wireless/rt2x00: don't use PREPARE_WORK in rt2800usb.c · 434bb46c
      由 Tejun Heo 提交于 
      PREPARE_[DELAYED_]WORK() are being phased out.  They have few users
and a nasty surprise in terms of reentrancy guarantee as workqueue
considers work items to be different if they don't have the same work
function.

Update rt2800usb.c to use INIT_WORK() instead of PREPARE_WORK().  As
the work item isn't in active use during rt2800usb_probe_hw(), this
doesn't cause any behavior difference.

It would probably be best to route this with other related updates
through the workqueue tree.

Only compile tested.
Signed-off-by: NTejun Heo <tj@kernel.org>
Cc: Ivo van Doorn <IvDoorn@gmail.com>
Cc: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>
Cc: linux-wireless@vger.kernel.org
Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      434bb46c
  17. 13 2月, 2014 1 次提交
  19. 05 2月, 2014 2 次提交
  21. 24 1月, 2014 1 次提交
  23. 04 1月, 2014 2 次提交
  25. 11 12月, 2013 1 次提交
  27. 06 12月, 2013 4 次提交
  29. 16 11月, 2013 1 次提交
  31. 15 11月, 2013 1 次提交
    • S
      kfifo API type safety · 498d319b
      由 Stefani Seibold 提交于 
      This patch enhances the type safety for the kfifo API.  It is now safe
to put const data into a non const FIFO and the API will now generate a
compiler warning when reading from the fifo where the destination
address is pointing to a const variable.

As a side effect the kfifo_put() does now expect the value of an element
instead a pointer to the element.  This was suggested Russell King.  It
make the handling of the kfifo_put easier since there is no need to
create a helper variable for getting the address of a pointer or to pass
integers of different sizes.

IMHO the API break is okay, since there are currently only six users of
kfifo_put().

The code is also cleaner by kicking out the "if (0)" expressions.

[akpm@linux-foundation.org: coding-style fixes]
Signed-off-by: NStefani Seibold <stefani@seibold.net>
Cc: Russell King <rmk@arm.linux.org.uk>
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      498d319b
  33. 12 11月, 2013 2 次提交
  35. 19 10月, 2013 15 次提交