]> git.ipfire.org Git - thirdparty/kernel/stable-queue.git/commit
projects / thirdparty / kernel / stable-queue.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: a38b63d) | patch
4.4-stable patches
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 18 May 2019 07:01:27 +0000 (09:01 +0200)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 18 May 2019 07:01:27 +0000 (09:01 +0200)
commite3f2be6d3e67b413643d1b060a4f8f0185b84835
tree390c11937545cf4b189e083a7ddd647fa6ed8698tree | snapshot
parenta38b63d1d59187db4f712dd116b16a5dbbb6c65ccommit | diff
4.4-stable patches

added patches:
crypto-arm-aes-neonbs-don-t-access-already-freed-walk.iv.patch
crypto-chacha20poly1305-set-cra_name-correctly.patch
crypto-gcm-fix-error-return-code-in-crypto_gcm_create_common.patch
crypto-gcm-fix-incompatibility-between-gcm-and-gcm_base.patch
crypto-salsa20-don-t-access-already-freed-walk.iv.patch
queue-4.4/crypto-arm-aes-neonbs-don-t-access-already-freed-walk.iv.patch [new file with mode: 0644] blob
queue-4.4/crypto-chacha20poly1305-set-cra_name-correctly.patch [new file with mode: 0644] blob
queue-4.4/crypto-gcm-fix-error-return-code-in-crypto_gcm_create_common.patch [new file with mode: 0644] blob
queue-4.4/crypto-gcm-fix-incompatibility-between-gcm-and-gcm_base.patch [new file with mode: 0644] blob
queue-4.4/crypto-salsa20-don-t-access-already-freed-walk.iv.patch [new file with mode: 0644] blob
queue-4.4/series diff | blob | blame | history
Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git