Tags give the ability to mark specific points in history as being important
-
sunxi-dt-for-5.5-2
74ab6d9d · ·A few more DT patches for 5.5, mostly: - USB3 support for the H6 - Deinterlacer support for the H3 - eDP Bridge support on the Teres-I - More DT cleanups thanks to the validation
-
sunxi-fixes-for-5.4-3
6b832a14 · ·One patch to add back the PMU node that was removed because the interrupts were improper in a previous fixes PR.
-
-
xfs-5.5-merge-9
9842b56c · ·New code for 5.5: - Fill out the build string - Prevent inode fork extent count overflows - Refactor the allocator to reduce long tail latency - Rework incore log locking a little to reduce spinning - Break up the xfs_iomap_begin functions into smaller more cohesive parts - Fix allocation alignment being dropped too early when the allocation request is for more blocks than an AG is large - Other small cleanups - Clean up file buftarg retrieval helpers - Hoist the resvsp and unresvsp ioctls to the vfs - Remove the undocumented biosize mount option, since it has never been mentioned as existing or supported on linux - Clean up some of the mount option printing and parsing - Enhance attr leaf verifier to check block structure - Check dirent and attr names for invalid characters before passing them to the vfs - Refactor open-coded bmbt walking - Fix a few places where we return EIO instead of EFSCORRUPTED after failing metadata sanity checks - Fix a synchronization problem between fallocate and aio dio corrupting the file length - Clean up various loose ends in the iomap and bmap code - Convert to the new mount api - Make sure we always log something when returning EFSCORRUPTED
-
-
ASB-2019-11-05_mainline
aefd2d63 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.19-q-release
3716d346 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.19-q
9045ee1f · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.19
806aeaeb · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.14-q-release
f3b9aac7 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.14-q
93b27559 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.14-p-release
05d954dc · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.14-p
da95ef93 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.14
6409e7e0 · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833
-
ASB-2019-11-05_4.9-q-release
502a526a · ·https://source.android.com/security/bulletin/2019-11-01 CVE-2019-2213 CVE-2019-2214 CVE-2019-2215 CVE-2019-11833