summaryrefslogtreecommitdiff
path: root/tstamping.h
AgeCommit message (Expand)AuthorFilesLines
2013-06-04tstamping: add header file for packet timestampingDaniel Borkmann1-0/+6
lect name='ignorews' onchange='this.form.submit();'>mode:
author彭东林 <pengdonglin@smartisan.com>2016-09-26 08:29:31 +0000
committerMark Brown <broonie@kernel.org>2016-09-26 09:43:34 -0700
commit94d215cc6fc5f0a5d202ed2b12fa0b14392cc2e4 (patch)
tree7e8b5a8b3e00fc4a38bd0a0e6cd1854befaf7bbb /sound
parentf11766143caa065b3aef4d794c104ea0f37ada76 (diff)
ASoC: dpcm: print dai_link name of BE other than FE.
When operating the BE, we should print out the dai_link name of BE other than FE. This is useful when analyzing the kernel log. Signed-off-by: Donglin Peng <pengdonglin@smartisan.com> Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'sound')
afe lock
Reports have surfaced of a lockdep splat complaining about an irq-safe -> irq-unsafe locking order in the xfs_buf_bio_end_io() bio completion handler. This only occurs when I/O errors are present because bp->b_lock is only acquired in this context to protect setting an error on the buffer. The problem is that this lock can be acquired with the (request_queue) q->queue_lock held. See scsi_end_request() or ata_qc_schedule_eh(), for example. Replace the locked test/set of b_io_error with a cmpxchg() call. This eliminates the need for the lock and thus the lock ordering problem goes away. Signed-off-by: Brian Foster <bfoster@redhat.com> Reviewed-by: Dave Chinner <dchinner@redhat.com> Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'Makefile')