summaryrefslogtreecommitdiff
path: root/include/crypto/sha256_base.h
diff options
context:
space:
mode:
authorEric Dumazet <edumazet@google.com>2017-02-02 10:50:48 -0800
committerDavid S. Miller <davem@davemloft.net>2017-02-03 16:18:00 -0500
commit362108b5adddac6f496acc40696e499defd56d62 (patch)
tree356660f0c4971657a9ee8d342a9658793b076afd /include/crypto/sha256_base.h
parentfb6113e688e0bf5bc3081d6ff02e8ad77fed3c7a (diff)
myri10ge: get rid of custom busy poll code
Compared to custom busy_poll, the generic NAPI one is simpler and removes a lot of code. It removes one atomic in the fast path (when busy poll is not in action) since we do not have to use an extra spinlock. Signed-off-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/crypto/sha256_base.h')
0 files changed, 0 insertions, 0 deletions
cutes `list_splice_tail_init' on `pch->work_list' under lock `pl330->lock', whereas in the rest of the code `pch->work_list' 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 'include/dt-bindings/gpio/meson8-gpio.h')