On Wed, 2022-04-27 at 10:40 +0200, Alexander Kanavin wrote:
> Dropped patches are either backports, were merged upstream,
> or upstream fixed the issue differently.
> 
> Signed-off-by: Alexander Kanavin <a...@linutronix.de>
> ---
>  ...Fix-drd-tests-shared_timed_mutex.cpp.patch |  26 +++
>  ...against-__GLIBC_PREREQ-for-musl-libc.patch |  36 ----
>  ...plement-linux-rseq-syscall-as-ENOSYS.patch | 198 ------------------
>  ...ster.c-Limit-rawmemchr-test-to-glibc.patch |  35 ----
>  .../0004-Fix-out-of-tree-builds.patch         | 176 ----------------
>  ...wrap.c-Fake-__GLIBC_PREREQ-with-musl.patch |  28 ---
>  ...{valgrind_3.18.1.bb => valgrind_3.19.0.bb} |  14 +-
>  7 files changed, 33 insertions(+), 480 deletions(-)
>  create mode 100644 
> meta/recipes-devtools/valgrind/valgrind/0001-Fix-drd-tests-shared_timed_mutex.cpp.patch
>  delete mode 100644 
> meta/recipes-devtools/valgrind/valgrind/0001-Guard-against-__GLIBC_PREREQ-for-musl-libc.patch
>  delete mode 100644 
> meta/recipes-devtools/valgrind/valgrind/0001-Implement-linux-rseq-syscall-as-ENOSYS.patch
>  delete mode 100644 
> meta/recipes-devtools/valgrind/valgrind/0001-str_tester.c-Limit-rawmemchr-test-to-glibc.patch
>  delete mode 100644 
> meta/recipes-devtools/valgrind/valgrind/0004-Fix-out-of-tree-builds.patch
>  delete mode 100644 
> meta/recipes-devtools/valgrind/valgrind/0005-tc20_verifywrap.c-Fake-__GLIBC_PREREQ-with-musl.patch
>  rename meta/recipes-devtools/valgrind/{valgrind_3.18.1.bb => 
> valgrind_3.19.0.bb} (95%)

Did that patch result in:

https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/3176
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/3176

?

Cheers,

RIchard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#164920): 
https://lists.openembedded.org/g/openembedded-core/message/164920
Mute This Topic: https://lists.openembedded.org/mt/90726569/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to