aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-kernel/cryptodev
diff options
context:
space:
mode:
authorRoss Burton <ross.burton@intel.com>2018-03-09 20:56:09 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-03-11 06:25:23 -0700
commit0666146a9f12c90e2b5f9fd3b03b21429fb9327c (patch)
treef6a4e4d02e1ffb1b7610b564797775e913282b0a /meta/recipes-kernel/cryptodev
parent77fb72c76c8a5b2229a32f36a913a3293e9d2b56 (diff)
downloadopenembedded-core-contrib-0666146a9f12c90e2b5f9fd3b03b21429fb9327c.tar.gz
blktrace: refresh patches
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. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/recipes-kernel/cryptodev')
0 files changed, 0 insertions, 0 deletions