Tags give the ability to mark specific points in history as being important
-
xfs-5.5-merge-17
798a9cad · ·Fixes for 5.5-rc1: - Fix a crash in the log setup code when log mounting fails - Fix a hang when allocating space on the realtime device - Fix a block leak when freeing space on the realtime device
-
4.9.205-64
782764b1 · · -
4.14.157-171
f0252119 · · -
acpi-5.5-rc1-2
b65d5630 · ·Additional ACPI updates for 5.5-rc1 - Fix locking issue in acpi_os_map_cleanup() leading to a race condition that can be harnessed for provoking a kernel panic from user space (Francesco Ruggeri). - Fix parameter check in acpi_bus_get_private_data() (Vamshi K Sthambamkadi). - Allow GPE 0xFF to be masked via kernel command line (Yunfeng Ye). - Add a new lid switch blacklist entry for Acer Switch 10 SW5-032 to the ACPI button driver (Hans de Goede). - Clean up Kconfig (Krzysztof Kozlowski).
-
pm-5.5-rc1-2
1e4230f5 · ·Additional power management updates for 5.5-rc1 - Avoid a race condition in the ACPI EC driver that may cause systems to be unable to leave suspend-to-idle (Rafael Wysocki). - Drop the "disabled" field, which is redundant, from struct cpuidle_state (Rafael Wysocki). - Reintroduce device PM QoS frequency constraints (temporarily introduced and than dropped during the 5.4 cycle) in preparation for adding QoS support to devfreq (Leonard Crestez). - Clean up indentation (in multiple places) and the cpuidle drivers help text in Kconfig (Krzysztof Kozlowski, Randy Dunlap).
-
ASB-2019-12-05_4.14
e6b1fb0e · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_mainline
96dc079c · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.19-q-release
3716d346 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.19-q
ead6fb73 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.19
f0719dcb · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.14-q-release
f3b9aac7 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.14-q
161911d5 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.14-p-release
5066c252 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.14-p
0cdad0a1 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.9-q-release
502a526a · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.9-q
a36b5017 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.9-p-release
0fdccb78 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.9-o-mr1
e557a751 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.9-o-release
1d533566 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510
-
ASB-2019-12-05_4.9-p
0a1e6a56 · ·https://source.android.com/security/bulletin/2019-12-01 CVE-2018-20961 CVE-2019-15220 CVE-2019-15239 CVE-2017-0648 CVE-2017-0510