-
ASB-2019-01-05_4.4-o-mr14edc2ede · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
ASB-2019-01-05_4.4-o-releasef2d09ee0 · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
ASB-2019-01-05_4.4-n-release0b990c32 · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
ASB-2019-01-05_4.4-p908e8699 · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
ASB-2019-01-05_4.4-ob55e7ac5 · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
ASB-2019-01-05_4.4-n1695253e · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
ASB-2019-01-05_4.4d08574b6 · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
ASB-2019-01-05_3.18-o-mr196320f81 · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
ASB-2019-01-05_3.18-o-releasec761e27c · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
ASB-2019-01-05_3.18-n-release765500b1 · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
ASB-2019-01-05_3.18fa261123 · ·
https://source.android.com/security/bulletin/2019-01-01 CVE-2018-10876 CVE-2018-10880 CVE-2018-10882 CVE-2018-13405 CVE-2018-18281 CVE-2018-17182 CVE-2018-10877
-
sound-fix-4.21-rc13e9ad24b · ·
sound fixes for 4.21-rc1 (or whatever the next) Among a few HD-audio fixes, the only significant one is the regression fix on some machines like Dell XPS due to the default binding changes. We ended up reverting the whole since the fix for ASoC HD-audio driver won't be available immediately.
-
devprop-4.21-rc1-2f4747b9c · ·
Device properties framework fixes for 4.21-rc1 Fix two potential NULL pointer dereferences found by Coverity in the software nodes code introduced recently (Colin Ian King).
-
topic/drmp-cleanup-2019-01-02dd7ece7f · ·
Make some drm headers self-contained with includes and forward declarations
-
devicetree-for-4.215801169a · ·
Devicetree updates for v4.21: - Initial support for DT bindings using json-schema language. This is the start of converting DT bindings from free-form text to a structured format. - Reworking of initrd address initialization. This moves to using the phys address instead of virt addr in the DT parsing code. This rework was motivated by CONFIG_DEV_BLK_INITRD causing unnecessary rebuilding of lots of files. - Fix stale phandle entries in phandle cache - DT overlay validation improvements. This exposed several memory leak bugs which have been fixed. - Use node name and device_type helper functions in DT code - Last remaining conversions to using %pOFn printk specifier instead of device_node.name directly - Create new common RTC binding doc and move all trivial RTC devices out of trivial-devices.txt. - New bindings for Freescale MAG3110 magnetometer, Cadence Sierra PHY, and Xen shared memory - Update dtc to upstream version v1.4.7-57-gf267e674d145
-
gpio-v4.21-1a7c23f8d · ·
This is the bulk of GPIO changes for the v4.21 kernel series: Core changes: - Some core changes are already in outside of this pull request as they came through the regulator tree, most notably devm_gpiod_unhinge() that removes devres refcount management from a GPIO descriptor. This is needed in subsystems such as regulators where the regulator core need to take over the reference counting and lifecycle management for a GPIO descriptor. - We dropped devm_gpiochip_remove() and devm_gpio_chip_match() as nothing needs it. We can bring it back if need be. - Add a global TODO so people see where we are going. This helps setting the direction now that we are two GPIO maintainers. - Handle the MMC CD/WP properties in the device tree core. (The bulk of patches activating this code is already merged through the MMC/SD tree.) - Augment gpiochip_request_own_desc() to pass a flag so we as gpiochips can request lines as active low or open drain etc even from ourselves. New drivers: - New driver for Cadence GPIO blocks. - New driver for Atmel SAMA5D2 PIOBU GPIO lines. Driver improvements: - A major refactoring of the PCA953x driver - this driver has been around for ages, and is now modernized to reduce code duplication that has stacked up and is using regmap to read write and cache registers. - Intel drivers are now maintained in a separate tree and start with a round of cleanups and unifications.