summaryrefslogtreecommitdiffstats
path: root/recipes-kernel/ceetm
diff options
context:
space:
mode:
authorC.R. Guo <chunrong.guo@nxp.com>2018-03-20 16:01:48 +0800
committerOtavio Salvador <otavio@ossystems.com.br>2018-04-02 10:30:13 -0300
commit49c5985d05e7442393c9cdc0933d231666f09065 (patch)
treecf82c6aba7169d4b8d0b78007364abcf1deed30f /recipes-kernel/ceetm
parent0dc0c701511959f1e71c97a3323ea012f3f92bb4 (diff)
downloadmeta-freescale-49c5985d05e7442393c9cdc0933d231666f09065.tar.gz
openssl-qoriq: refresh patches
1. The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed 2. drop openssl-1.0.2a-x32-asm.patch The patch was applied in a completely incorrect spot (due to fuzz), no one noticed or complained. Meanwhile upstream says the issue has been resolved differently: https://rt.openssl.org/Ticket/Display.html?id=3759&user=guest&pass=guest Signed-off-by: Chunrong Guo <chunrong.guo@nxp.com> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Diffstat (limited to 'recipes-kernel/ceetm')
0 files changed, 0 insertions, 0 deletions