[OE-core] [PATCH] ltp: 20160126 -> 20160920

[Liu, Le (Charles)]

Hi Xin,

I just tried your patch on qemux86-64 BSP. It looks working well, except for the following two minor issues on patching.   

1.  I have to remove some "/dev/null" from the patch manually, before it was applied successfully. 

 $ diff ~/\[OE-core\]\ \[PATCH\]\ ltp\:\ 20160126\ -\>\ 20160920.eml /original_oe-core/\[OE-core\]\ \[PATCH\]\ ltp\:\ 20160126\ -\>\ 20160920.eml 
200a201
> --- /dev/null
238a240
> +++ /dev/null
272a275
> --- /dev/null
508a512
> --- /dev/null
680a685
> --- /dev/null
734a740
> +++ /dev/null
770a777
> +++ /dev/null
1169a1177
> +++ /dev/null
1585a1594
> +++ /dev/null
1941a1951
> +++ /dev/null
2013a2024
> +++ /dev/null
2074a2086
> +++ /dev/null
2143a2156
> +++ /dev/null
2193a2207
> +++ /dev/null
2286a2301
> +++ /dev/null
2323a2339
> +++ /dev/null
2357a2374
> +++ /dev/null
2391a2409
> +++ /dev/null
2428a2447
> +++ /dev/null
2466a2486
> +++ /dev/null
2504a2525
> +++ /dev/null


2. There are Hunk issues during patching "0011-Rename-sigset-variable-to-sigset1.patch".

...
Applying patch 0011-Rename-sigset-variable-to-sigset1.patch
patching file testcases/kernel/mem/shmt/shmt04.c
Hunk #1 FAILED at 56.
Hunk #2 FAILED at 71.
Hunk #3 FAILED at 148.
3 out of 3 hunks FAILED -- saving rejects to file testcases/kernel/mem/shmt/shmt04.c.rej
patching file testcases/kernel/mem/shmt/shmt06.c
Hunk #1 FAILED at 57.
Hunk #2 FAILED at 70.
Hunk #3 FAILED at 147.
3 out of 3 hunks FAILED -- saving rejects to file testcases/kernel/mem/shmt/shmt06.c.rej
patching file testcases/kernel/syscalls/sigprocmask/sigprocmask01.c
Hunk #1 FAILED at 91.
Hunk #2 FAILED at 112.
Hunk #3 FAILED at 165.
Hunk #4 FAILED at 212.
Hunk #5 FAILED at 235.
5 out of 5 hunks FAILED -- saving rejects to file testcases/kernel/syscalls/sigprocmask/sigprocmask01.c.rej
Applied patch 0011-Rename-sigset-variable-to-sigset1.patch (forced; needs refresh)




These might be related with the patching method I used (git am --keep-cr ~/\[OE-core\]\ \[PATCH\]\ ltp\:\ 20160126\ -\>\ 20160920.eml). Could you help to confirm?


Thanks,
Charles