bnxt_en: Added PCI IDs for BCM57452 and BCM57454 ASICs - net-next.git - net-next plumbings

summary refs log tree commit diff

path: root/net/ipv6/ip6_input.c

diff options

author	Deepak Khungar <deepak.khungar@broadcom.com>	2017-02-12 19:18:18 -0500
committer	David S. Miller <davem@davemloft.net>	2017-02-12 22:18:49 -0500
commit	32b40798c1b40343641f04cdfd09652af70ea0e9 (patch)
tree	9d14df9b9731493be45194bc9360de8812cb3f91 /net/ipv6/ip6_input.c
parent	b451c8b69e70de299aa6061e1fa6afbb4d7c1f9e (diff)

bnxt_en: Added PCI IDs for BCM57452 and BCM57454 ASICs

Signed-off-by: Deepak Khungar <deepak.khungar@broadcom.com> Signed-off-by: Michael Chan <michael.chan@broadcom.com> Signed-off-by: David S. Miller <davem@davemloft.net>

Diffstat (limited to 'net/ipv6/ip6_input.c')

0 files changed, 0 insertions, 0 deletions

ources' executes `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 'sound/core/oss/pcm_oss.c')