-
iio-fixes-for-4.16b8b438686 · ·
Second set of IIO fixes for the 4.16 cycle. A slightly fiddly revert then fix pair in here as the bug lead to an unused local variable that was then removed without us noticing the bug. The revert should only be needed on 4.16 - the fix goes back futher. * ccs811 - Fix the transition from 'boot' to 'application' mode. Fixes the case where the power is not cut between boot cycles. * meson-saradc - Fix missing mutex_unlock in an error path. * sd-modulator - Fix bindings doc to have the right value of io-channel-cells to reflect that this device type only ever outputs one channel. * st-accel - Revert drop of redundant pointer patch. - Use the now available pointer to avoid overwriting the platform data pointer and causing trouble on reprobing the driver. * st-pressure - Use local copy of the platform data pointer to avoid overwriting the one associated with the device, which would cause issues on reprobing the driver. * stm32-dfsdm - Use the right regmap_cfg for the type of device. - Correct the ID passed to stop channel to be the channel one. - Correct which clock is used to allow for the 'audio' clock. - Fix allocation of channels when more than one is enabled. -
gpio-v4.16-39ac79ba9 · ·
This is a single GPIO fix for the v4.16 series affecting the Renesas driver, and fixes wakeup from external stuff.
-
drm-misc-next-2018-03-09-360beeccc · ·
drm-misc-next for 4.17: UAPI Changes: plane: Add color encoding/range properties (Jyri) nouveau: Replace iturbt_709 property with color_encoding property (Ville) Core Changes: atomic: Move plane clipping into plane check helper (Ville) property: Multiple new property checks/verification (Ville) Driver Changes: rockchip: Fixes & improvements for rk3399/chromebook plus (various) sun4i: Add H3/H5 HDMI support (Jernej) i915: Add support for limited/full-range ycbcr toggling (Ville) pl111: Add bandwidth checking/limiting (Linus) Cc: Jernej Skrabec <jernej.skrabec@siol.net> Cc: Jyri Sarha <jsarha@ti.com> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Cc: Linus Walleij <linus.walleij@linaro.org>
-
sound-4.16-rc5099fd6ca · ·
sound fixes for 4.16-rc5 Two type of fixes: - The usual stuff, a handful HD-audio quirks for various machines - Further hardening against ALSA sequencer ioctl/write races that are triggered by fuzzer
-
drm-fixes-for-v4.16-rc5
amdgfx, i915, sun4i fixes
-
wireless-drivers-for-davem-2018-03-08455f3e76 · ·
wireless-drivers fixes for 4.16 Quote a few fixes as I have not been able to send a pull request earlier. Most of the fixes for iwlwifi but also few others, nothing really standing out though. iwlwifi * fix a bogus warning when freeing a TFD * fix severe throughput problem with 9000 series * fix for a bug that caused queue hangs in certain situations * fix for an issue with IBSS * fix an issue with rate-scaling in AP-mode * fix Channel Switch Announcement (CSA) issues with count 0 and 1 * some firmware debugging fixes * remov a wrong error message when removing keys * fix a firmware sysassert most usually triggered in IBSS * a couple of fixes on multicast queues * a fix with CCMP 256 rtlwifi * fix loss of signal for rtl8723be brcmfmac * add possibility to obtain firmware error * fix P2P_DEVICE ethernet address generation
-
drm-intel-next-2018-03-08cf07a60f · ·
UAPI Changes: - Query uAPI interface (used for GPU topology information currently) * Mesa: https://patchwork.freedesktop.org/series/38795/ Driver Changes: - Increase PSR2 size for CNL (DK) - Avoid retraining LSPCON link unnecessarily (Ville) - Decrease request signaling latency (Chris) - GuC error capture fix (Daniele)
-
regulator-fix-v4.16-rc482a917c5 · ·
regulator: Fixes for v4.16 A couple of fixes here: - Another half of the supend to idle fix from Geert that went in earlier, both he and I are confused as to why he didn't notice that this was missing when his earlier fix was merged. - A simple fix for a test done the wrong way round in the stm32-vrefbuf driver.
-
ASB-2018-03-05_4.9-o-mr16202fd7b · ·
https://source.android.com/security/bulletin/2018-03-01 CVE-2016-8405 CVE-2017-13216 CVE-2017-17770 CVE-2017-15129 CVE-2017-16530 CVE-2017-16525 CVE-2017-5754 CVE-2017-16535 CVE-2017-16533 CVE-2017-16531 CVE-2017-16529
-
ASB-2018-03-05_4.9-o-release50d5695a · ·
https://source.android.com/security/bulletin/2018-03-01 CVE-2016-8405 CVE-2017-13216 CVE-2017-17770 CVE-2017-15129 CVE-2017-16530 CVE-2017-16525 CVE-2017-5754 CVE-2017-16535 CVE-2017-16533 CVE-2017-16531 CVE-2017-16529
-
ASB-2018-03-05_4.4-o-mr1ac6a8fa7 · ·
https://source.android.com/security/bulletin/2018-03-01 CVE-2016-8405 CVE-2017-13216 CVE-2017-17770 CVE-2017-15129 CVE-2017-16530 CVE-2017-16525 CVE-2017-5754 CVE-2017-16535 CVE-2017-16533 CVE-2017-16531 CVE-2017-16529
-
ASB-2018-03-05_4.4-o-releasefb32c1a6 · ·
https://source.android.com/security/bulletin/2018-03-01 CVE-2016-8405 CVE-2017-13216 CVE-2017-17770 CVE-2017-15129 CVE-2017-16530 CVE-2017-16525 CVE-2017-5754 CVE-2017-16535 CVE-2017-16533 CVE-2017-16531 CVE-2017-16529
-
ASB-2018-03-05_4.4-n-release1dd1f752 · ·
https://source.android.com/security/bulletin/2018-03-01 CVE-2016-8405 CVE-2017-13216 CVE-2017-17770 CVE-2017-15129 CVE-2017-16530 CVE-2017-16525 CVE-2017-5754 CVE-2017-16535 CVE-2017-16533 CVE-2017-16531 CVE-2017-16529
-
ASB-2018-03-05_3.18-o-mr17f69e880 · ·
https://source.android.com/security/bulletin/2018-03-01 CVE-2016-8405 CVE-2017-13216 CVE-2017-17770 CVE-2017-15129 CVE-2017-16530 CVE-2017-16525 CVE-2017-5754 CVE-2017-16535 CVE-2017-16533 CVE-2017-16531 CVE-2017-16529
-
ASB-2018-03-05_3.18-o-releasee521f3de · ·
https://source.android.com/security/bulletin/2018-03-01 CVE-2016-8405 CVE-2017-13216 CVE-2017-17770 CVE-2017-15129 CVE-2017-16530 CVE-2017-16525 CVE-2017-5754 CVE-2017-16535 CVE-2017-16533 CVE-2017-16531 CVE-2017-16529