-
sunxi-clk-for-5.69c232d32 · ·
Our usual set of patches for sunxi, with a bunch of them required to enable the MBUS controller, and two patches to enable cpufreq on the A64.
-
pm-5.5-rc610674d97 · ·
Power management fixes for 5.5-rc6 Prevent the cpufreq-dt driver from probing Tegra20/30 (Dmitry Osipenko) and prevent the Intel RAPL power capping driver from crashing during CPU initialization due to a NULL pointer dereference if the processor model in use is not known to it (Harry Pan).
-
amd-drm-next-5.6-2020-01-09-dp-mst-dsc9edb435a · ·
amd-drm-next-5.6-2020-01-09-dp-mst-dsc: drm: - Add MST helper for PBN calculation of DSC modes - Parse FEC caps on MST ports - Add MST DPCD R/W functions - Add MST helpers for virtual DPCD aux - Add MST HUB quirk - Add MST DSC enablement helpers amdgpu: - Enable MST DSC - Add fair share algo for DSC bandwidth calcs
-
amd-drm-next-5.6-2020-01-090f899fd4 · ·
amd-drm-next-5.6-2020-01-09: amdgpu: - Enable DCN support on POWER - Enable GFXOFF for Raven1 refresh - Clean up MM engine idle handlers - HDMI 2.0 audio fixes - Fixes for some 10 bpc EDP panels - Watermark fixes for renoir - SR-IOV fixes - Runtime pm robustness fixes - Arcturus VCN fixes - RAS fixes - BACO fixes for Arcturus - Stable pstate fixes for swSMU - HDCP fixes - PSP cleanup - HDMI fixes - Misc cleanups amdkfd: - Spread interrupt work across cores to reduce latency - Topology fixes for APUs - GPU reset improvements UAPI: - Enable DRIVER_SYNCOBJ_TIMELINE for vulkan - Return better error values for kfd process ioctl
-
amd-drm-fixes-5.5-2020-01-08db4ff423 · ·
amd-drm-fixes-5.5-2020-01-08: amdgpu: - Stability fix for raven - Reduce pixel encoding to if max clock is exceeded on HDMI to allow additional high res modes UAPI: - enable DRIVER_SYNCOBJ_TIMELINE for amdgpu
-
ASB-2020-01-05_mainlinea931d512 · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214
-
ASB-2020-01-05_5.420810a24 · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214
-
ASB-2020-01-05_4.19-q-release3716d346 · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214
-
ASB-2020-01-05_4.19-q5d7443e6 · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214
-
ASB-2020-01-05_4.19e782153f · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214
-
ASB-2020-01-05_4.14-q-release5a917b45 · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214
-
ASB-2020-01-05_4.14-q0329b4d6 · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214
-
ASB-2020-01-05_4.14-p-release0e792837 · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214
-
ASB-2020-01-05_4.14-pe2938fe7 · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214
-
ASB-2020-01-05_4.147742890e · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214
-
ASB-2020-01-05_4.9-q-release9aa79c17 · ·
https://source.android.com/security/bulletin/2020-01-01 CVE-2019-17666 CVE-2018-20856 CVE-2019-11599 CVE-2019-15214