linux_dsm_epyc7002/drivers/net/ethernet/intel
Will Deacon fb24ea52f7 drivers: Remove explicit invocations of mmiowb()
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: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Will Deacon <will.deacon@arm.com>
2019-04-08 12:01:02 +01:00
..
e1000 drivers: Remove explicit invocations of mmiowb() 2019-04-08 12:01:02 +01:00
e1000e drivers: Remove explicit invocations of mmiowb() 2019-04-08 12:01:02 +01:00
fm10k drivers: Remove explicit invocations of mmiowb() 2019-04-08 12:01:02 +01:00
i40e drivers: Remove explicit invocations of mmiowb() 2019-04-08 12:01:02 +01:00
iavf drivers: Remove explicit invocations of mmiowb() 2019-04-08 12:01:02 +01:00
ice drivers: Remove explicit invocations of mmiowb() 2019-04-08 12:01:02 +01:00
igb drivers: Remove explicit invocations of mmiowb() 2019-04-08 12:01:02 +01:00
igbvf drivers: Remove explicit invocations of mmiowb() 2019-04-08 12:01:02 +01:00
igc drivers: Remove explicit invocations of mmiowb() 2019-04-08 12:01:02 +01:00
ixgb
ixgbe drivers: Remove explicit invocations of mmiowb() 2019-04-08 12:01:02 +01:00
ixgbevf
e100.c
Kconfig
Makefile