Linux Kernel https://git.etezian.org/cgit.cgi/linux.git/atom?h=master 2017-02-14T14:29:21+00:00 2017-02-14T14:29:21+00:00 Linus Torvalds torvalds@linux-foundation.org 2017-02-14T14:29:21+00:00 urn:sha1:747ae0a96f1a78b35c5a3d93ad37a16655e16340 Pull media fixes from Mauro Carvalho Chehab: "A colorspace regression fix in V4L2 core and a CEC core bug that makes it discard valid messages" * tag 'media/v4.10-4' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media: [media] cec: initiator should be the same as the destination for, poll [media] videodev2.h: go back to limited range Y'CbCr for SRGB and, ADOBERGB 2017-02-13T16:34:11+00:00 Hans Verkuil hverkuil@xs4all.nl 2017-02-11T11:24:46+00:00 urn:sha1:42980da2eb7eb9695d8efc0c0ef145cbbb993b2c Poll messages that are used to allocate a logical address should use the same initiator as the destination. Instead, it expected that the initiator was 0xf which is not according to the standard. This also had consequences for the message checks in cec_transmit_msg_fh that incorrectly rejected poll messages with the same initiator and destination. Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com> 2017-02-13T16:33:56+00:00 Hans Verkuil hverkuil@xs4all.nl 2017-02-10T09:18:36+00:00 urn:sha1:35879ee4769099905fa3bda0b21e73d434e2df6a This reverts 'commit 7e0739cd9c40 ("[media] videodev2.h: fix sYCC/AdobeYCC default quantization range"). The problem is that many drivers can convert R'G'B' content (often from sensors) to Y'CbCr, but they all produce limited range Y'CbCr. To stay backwards compatible the default quantization range for sRGB and AdobeRGB Y'CbCr encoding should be limited range, not full range, even though the corresponding standards specify full range. Update the V4L2_MAP_QUANTIZATION_DEFAULT define accordingly and also update the documentation. Fixes: 7e0739cd9c40 ("[media] videodev2.h: fix sYCC/AdobeYCC default quantization range") Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Cc: <stable@vger.kernel.org> # for v4.9 and up Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com> 2017-02-12T21:03:20+00:00 Linus Torvalds torvalds@linux-foundation.org 2017-02-12T21:03:20+00:00 urn:sha1:7089db84e356562f8ba737c29e472cc42d530dbc 2017-02-11T18:31:46+00:00 Linus Torvalds torvalds@linux-foundation.org 2017-02-11T18:31:46+00:00 urn:sha1:1ce42845f987e92eabfc6e026d44d826c25c74a5 Pull x86 fixes from Ingo Molnar: "Last minute x86 fixes: - Fix a softlockup detector warning and long delays if using ptdump with KASAN enabled. - Two more TSC-adjust fixes for interesting firmware interactions. - Two commits to fix an AMD CPU topology enumeration bug that caused a measurable gaming performance regression" * 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: x86/mm/ptdump: Fix soft lockup in page table walker x86/tsc: Make the TSC ADJUST sanitizing work for tsc_reliable x86/tsc: Avoid the large time jump when sanitizing TSC ADJUST x86/CPU/AMD: Fix Zen SMT topology x86/CPU/AMD: Bring back Compute Unit ID 2017-02-11T18:24:16+00:00 Linus Torvalds torvalds@linux-foundation.org 2017-02-11T18:24:16+00:00 urn:sha1:fdb0ee7c65781464168e2943a3fd6f1e66a397c9 Pull timer fix from Ingo Molnar: "Fix a sporadic missed timer hw reprogramming bug that can result in random delays" * 'timers-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: tick/nohz: Fix possible missing clock reprog after tick soft restart 2017-02-11T18:20:06+00:00 Linus Torvalds torvalds@linux-foundation.org 2017-02-11T18:20:06+00:00 urn:sha1:d5b76bef01047843cc65bd018046c76182b1fc81 Pull perf fixes from Ingo Molnar: "A kernel crash fix plus three tooling fixes" * 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: perf/core: Fix crash in perf_event_read() perf callchain: Reference count maps perf diff: Fix -o/--order option behavior (again) perf diff: Fix segfault on 'perf diff -o N' option 2017-02-11T18:16:05+00:00 Linus Torvalds torvalds@linux-foundation.org 2017-02-11T18:16:05+00:00 urn:sha1:4e4f74a7eebbc52eaa1dc3c0be6b3c68c0875b09 Pull lockdep fix from Ingo Molnar: "This fixes an ugly lockdep stack trace output regression. (But also affects other stacktrace users such as kmemleak, KASAN, etc)" * 'locking-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: stacktrace, lockdep: Fix address, newline ugliness 2017-02-11T18:14:24+00:00 Linus Torvalds torvalds@linux-foundation.org 2017-02-11T18:14:24+00:00 urn:sha1:21a7061c5ec300a8a12a0d6468eb7094e9c54a32 Pull irq fixes from Ingo Molnar: "Two last minute ARM irqchip driver fixes" * 'irq-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: irqchip/mxs: Enable SKIP_SET_WAKE and MASK_ON_SUSPEND irqchip/keystone: Fix "scheduling while atomic" on rt 2017-02-11T17:15:58+00:00 Linus Torvalds torvalds@linux-foundation.org 2017-02-11T17:15:58+00:00 urn:sha1:2b95550a4323e501e133dac1c9c9cad6ff17f4c1 Pull btrfs fixes from Chris Mason: "This has two last minute fixes. The highest priority here is a regression fix for the decompression code, but we also fixed up a problem with the 32-bit compat ioctls. The decompression bug could hand back the wrong data on big reads when zlib was used. I have a larger cleanup to make the math here less error prone, but at this stage in the release Omar's patch is the best choice" * 'for-linus-4.10' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs: btrfs: fix btrfs_decompress_buf2page() btrfs: fix btrfs_compat_ioctl failures on non-compat ioctls