1. 25 8月, 2020 1 次提交
  2. 23 7月, 2020 1 次提交
  3. 21 7月, 2020 5 次提交
  4. 16 7月, 2020 1 次提交
  5. 07 7月, 2020 1 次提交
  6. 01 7月, 2020 2 次提交
  7. 15 5月, 2020 3 次提交
  8. 18 4月, 2020 1 次提交
  9. 27 1月, 2020 3 次提交
  10. 11 9月, 2019 1 次提交
  11. 01 9月, 2019 2 次提交
  12. 16 8月, 2019 1 次提交
  13. 09 8月, 2019 1 次提交
  14. 27 5月, 2019 1 次提交
  15. 08 4月, 2019 1 次提交
    • W
      drivers: Remove explicit invocations of mmiowb() · fb24ea52
      Will Deacon 提交于
      mmiowb() is now implied by spin_unlock() on architectures that require
      it, so there is no reason to call it from driver code. This patch was
      generated using coccinelle:
      
      	@mmiowb@
      	@@
      	- mmiowb();
      
      and invoked as:
      
      $ for d in drivers include/linux/qed sound; do \
      spatch --include-headers --sp-file mmiowb.cocci --dir $d --in-place; done
      
      NOTE: mmiowb() has only ever guaranteed ordering in conjunction with
      spin_unlock(). However, pairing each mmiowb() removal in this patch with
      the corresponding call to spin_unlock() is not at all trivial, so there
      is a small chance that this change may regress any drivers incorrectly
      relying on mmiowb() to order MMIO writes between CPUs using lock-free
      synchronisation. If you've ended up bisecting to this commit, you can
      reintroduce the mmiowb() calls using wmb() instead, which should restore
      the old behaviour on all architectures other than some esoteric ia64
      systems.
      Acked-by: NLinus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: NWill Deacon <will.deacon@arm.com>
      fb24ea52
  16. 09 2月, 2019 1 次提交
  17. 29 1月, 2019 1 次提交
  18. 26 1月, 2019 1 次提交
  19. 23 1月, 2019 1 次提交
  20. 18 1月, 2019 1 次提交
  21. 01 12月, 2018 2 次提交
  22. 17 10月, 2018 1 次提交
  23. 03 10月, 2018 1 次提交
  24. 20 7月, 2018 1 次提交
  25. 01 6月, 2018 1 次提交
  26. 26 5月, 2018 1 次提交
  27. 23 5月, 2018 3 次提交