summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/efivarfs/open-unlink.c
diff options
context:
space:
mode:
authorEric Dumazet <edumazet@google.com>2017-02-04 15:24:59 -0800
committerDavid S. Miller <davem@davemloft.net>2017-02-05 16:11:57 -0500
commit0eb7b85c9669fce5ebf22915ee5f93b6d721256e (patch)
tree08a92b083a910f26bc01e35ef367b8509111ecc7 /tools/testing/selftests/efivarfs/open-unlink.c
parent7ea4007757e56bd2fb589820ba7676d2dfb0b47a (diff)
qla3xxx: add GRO support
Use napi_complete_done() instead of __napi_complete() to : 1) Get support of gro_flush_timeout if opt-in 2) Not rearm interrupts for busy-polling users. 3) use standard NAPI API. Signed-off-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/testing/selftests/efivarfs/open-unlink.c')
0 files changed, 0 insertions, 0 deletions
ist' is protected by `pch->lock'. I don't know if this may cause race conditions. Similarly `pch->cyclic' is written by `pl330_alloc_chan_resources' under `pl330->lock' but read by `pl330_tx_submit' under `pch->lock'. Second, I have removed locking from `pl330_request_channel' and `pl330_release_channel' functions. Function `pl330_request_channel' is only called from `pl330_alloc_chan_resources', so the lock is already held. Function `pl330_release_channel' is called from `pl330_free_chan_resources', which already holds the lock, and from `pl330_del'. Function `pl330_del' is called in an error path of `pl330_probe' and at the end of `pl330_remove', but I assume that there cannot be concurrent accesses to the protected data at those points. Signed-off-by: Iago Abal <mail@iagoabal.eu> Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'tools/perf/arch/x86/include/dwarf-regs-table.h')