Tags give the ability to mark specific points in history as being important
-
-
drm-intel-next-2017-12-22
cfe4982c · ·- Allow internal page allocation to fail (Chris) - More improvements on logs, dumps, and trace (Chris, Michal) - Coffee Lake important fix for stolen memory (Lucas) - Continue to make GPU reset more robust as well improving selftest coverage for it (Chris) - Unifying debugfs return codes (Michal) - Using existing helper for testing obj pages (Matthew) - Organize and improve gem_request tracepoints (Lionel) - Protect DDI port to DPLL map from theoretical race (Rodrigo) - ... and consequently fixing the indentation on this DDI clk selection function (Chris) - ... and consequently properly serializing non-blocking modesets (Ville) - Add support for horizontal plane flipping on Cannonlake (Joonas) - Two Cannonlake Workarounds for better stability (Rafael) - Fix mess around PSR registers (DK) - More Coffee Lake PCI IDs (Rodrigo) - Remove CSS modifiers on pipe C of Geminilake (Krisman) - Disable all planes for load detection (Ville) - Reorg on i915 display headers (Michal) - Avoid enabling movntdqa optimization on hypervisor guest (Changbin) GVT: - more mmio switch optimization (Weinan) - cleanup i915_reg_t vs. offset usage (Zhenyu) - move write protect handler out of mmio handler (Zhenyu)
-
-
-
-
drm-misc-next-2017-12-21
8d44e9e6 · ·drm-misc-next for 4.16: Core Changes: - mostly doc updates and some fbdev improvements
-
xfs-4.15-fixes-8
68c58e9b · ·Changes since last update: - Fix a locking problem during xattr block conversion that could lead to the log checkpointing thread to try to write an incomplete buffer to disk, which leads to a corruption shutdown - Fix a null pointer dereference when removing delayed allocation extents - Remove post-eof speculative allocations when reflinking a block past current inode size so that we don't just leave them there and assert on inode reclaim - Relax an assert which didn't accurately reflect the way locking works and would trigger under heavy io load - Avoid infinite loop when cancelling copy on write extents after a writeback failure - Try to avoid copy on write transaction reservation overflows when remapping after a successful write - Fix various problems with the copy-on-write reservation automatic garbage collection not being cleaned up properly during a ro remount - Fix problems with rmap log items being processed in the wrong order, leading to corruption shutdowns - Fix problems with EFI recovery wherein the "remove any rmapping if present" mechanism wasn't actually doing anything, which would lead to corruption problems later when the extent is reallocated, leading to multiple rmaps for the same extent
-
drm-misc-fixes-2017-12-21
d2a48e52 · ·drm-misc-fixes before holidays: - fixup for the lease fixup (Keith) - fb leak in the ww mutex fallback code (Maarten) - sun4i fixes (Maxime, Hans)
-
acpi-4.15-rc5
9245fe9f · ·ACPI fixes for v4.15-rc5 - Fix an error handling issue in the ACPI APEI implementation of the >read callback in struct pstore_info (Takashi Iwai). - Fix a possible out-of-bounds arrar read in the ACPI CPPC driver (Colin Ian King).
-
pm-4.15-rc5
63d15e8c · ·Power management fixes for v4.15-rc5 - Fix an issue in the PCI handling of the "thaw" transition during hibernation (after creating an image), introduced by a bug fix from the 4.13 cycle and exposed by recent changes in the IRQ subsystem, that caused pci_restore_state() to be called for devices in low-power states in some cases which is incorrect and breaks MSI management on some systems (Rafael Wysocki). - Fix a recent regression in the imx6q cpufreq driver that broke speed grading on i.MX6 QuadPlus by omitting checks causing invalid operating performance points (OPPs) to be disabled on that SoC as appropriate (Lucas Stach). - Fix a regression introduced during the 4.14 cycle in the ondemand and conservative cpufreq governors that causes the sampling interval used by them to be shorter than the tick period in some cases which leads to incorrect decisions (Rafael Wysocki).
-
-
-
-
-
-
ASB-2017-12-05_4.9-o-mr1
22e9a46b · ·https://source.android.com/security/bulletin/2017-12-01 Required: CVE-2017-7533 CVE-2017-13166 Recommended: CVE-2017-15868 CVE-2017-1000380
-
ASB-2017-12-05_4.9-o-release
c80cb166 · ·https://source.android.com/security/bulletin/2017-12-01 Required: CVE-2017-7533 CVE-2017-13166 Recommended: CVE-2017-15868 CVE-2017-1000380
-
ASB-2017-12-05_4.4-o-mr1
554843b5 · ·https://source.android.com/security/bulletin/2017-12-01 Required: CVE-2017-7533 CVE-2017-13166 Recommended: CVE-2017-15868 CVE-2017-1000380
-
ASB-2017-12-05_4.4-o-release
83fbd12c · ·https://source.android.com/security/bulletin/2017-12-01 Required: CVE-2017-7533 CVE-2017-13166 Recommended: CVE-2017-15868 CVE-2017-1000380
-
ASB-2017-12-05_4.4-n-release
4395789b · ·https://source.android.com/security/bulletin/2017-12-01 Required: CVE-2017-7533 CVE-2017-13166 Recommended: CVE-2017-15868 CVE-2017-1000380