Tags give the ability to mark specific points in history as being important
-
ASB-2017-11-06_3.18-n-release
996bacc8 · ·https://source.android.com/security/bulletin/2017-11-01 CVE-2017-9077 CVE-2017-7541
-
drm-misc-next-fixes-2017-11-07
e073db5c · ·Fixes for 4.15 merge window: Just the cherry-picked vc4 fix plus a GFP_NOFAIL annotation (there's apparently some new options in-flight to change/audit too-small-to-fail kmalloc semantics or something like that).
-
-
sunxi-dt64-for-4.15-2
16416084 · ·Allwinner arm64 changes, take 2 Reintroduction of the EMAC bindings that were reverted in 4.13.
-
sunxi-dt-for-4.15-2
f2f221c7 · ·Allwinner DT changes for 4.15, take 2 Two long awaited changes: - Reintroduction of the new EMAC DT bindings that got reverted at the last minute in 4.13 - Introduction of the AXP803/813 PMIC support -
-
-
drm-fixes-for-v4.14-rc8
i915, amdgpu and nouveau fixes
-
drm-misc-fixes-2017-11-02
62676d10 · ·Driver Changes: - qxl: Use a shadow bo as primary and blit to it to fix flicker (Gerd)
-
-
-
-
-
drm-intel-fixes-2017-11-01
bb5cf338 · ·Fixes for Stable: - Fix KBL Blank Screen (Jani) - Fix FIFO Underrun on SNB (Maarten) Other fixes: - Fix GPU Hang on i915gm (Chris) - Fix gem_tiled_pread_pwrite IGT case (Chris) - Cancel modeset retry work during modeset clean-up (Manasi)
-
pm-reverts-4.14
d5919dcc · ·Power management commit reverts for v4.14 This reverts two recent PM QoS commits one of which introduced multiple problems and the other one fixed some, but not all of them (Rafael Wysocki).
-
wireless-drivers-for-davem-2017-10-31
c29f56b9 · ·wireless-drivers fixes for 4.14 The most important here is the security vulnerabitility fix for ath10k. ath10k * fix security vulnerability with missing PN check on certain hardware * revert ath10k napi fix as it caused regressions on QCA6174 wcn36xx * remove unnecessary rcu_read_unlock() from error path
-
pm-urgent-4.14
2a9a86d5 · ·Urgent power management fix for v4.14 This fixes new breakage introduced by the most recent PM QoS fix in which, embarrassingly enough, I forgot to update dev_pm_qos_raw_read_value() to return the right default for devices with no PM QoS constraints at all which prevents runtime PM from suspending those devices (fix from Tero Kristo).
-
-
-