summaryrefslogtreecommitdiff
path: root/net/dns_resolver/Kconfig
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-02-02 12:39:10 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-02-02 12:39:10 -0800
commite4178c75049c581114998a850ecdfa5a2811cde6 (patch)
tree30ad09d949e58d32a4c0aa0a70bc1819a26d820d /net/dns_resolver/Kconfig
parentf2557779e1a9cfbf69c99b74da26cc1b2b10e752 (diff)
parent4b3e6f2ef3722f1a6a97b6034ed492c1a21fd4ae (diff)
Merge tag 'xtensa-20170202' of git://github.com/jcmvbkbc/linux-xtensa
Pull Xtensa fix from Max Filippov: "A for an Xtensa build error introduced in reset code refactoring series in v4.9: - fix noMMU build on cores with MMU" * tag 'xtensa-20170202' of git://github.com/jcmvbkbc/linux-xtensa: xtensa: fix noMMU build on cores with MMU
Diffstat (limited to 'net/dns_resolver/Kconfig')
0 files changed, 0 insertions, 0 deletions
_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/pmu-events/arch/x86/haswell/virtual-memory.json')