public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 13/18] valgrind: update 3.18.1 -> 3.19.0
Date: Wed, 27 Apr 2022 15:37:41 +0100	[thread overview]
Message-ID: <d90f055950c3891d373d2fdec2358f902d4564de.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj9eUzy9-6wLZ3rLpr+cAno33VosPr6qVEBWHt9D8GGbcg@mail.gmail.com>

On Wed, 2022-04-27 at 16:34 +0200, Alexander Kanavin wrote:
> On Wed, 27 Apr 2022 at 15:08, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > Did that patch result in:
> > 
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/3176
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/3176
> 
> A previous version of it, yes. I addressed the issues:
> 
> +           file://0001-Fix-drd-tests-shared_timed_mutex.cpp.patch \
> 
> +    # https://bugs.kde.org/show_bug.cgi?id=445743
> +    rm ${D}${PTEST_PATH}/drd/tests/pth_mutex_signal
> 

Great, thanks. I just wasn't 100% sure and I'm feeling a little paranoid! :)

Cheers,

Richard



  reply	other threads:[~2022-04-27 14:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  8:39 [PATCH 01/18] libxml2: update patch status Alexander Kanavin
2022-04-27  8:39 ` [PATCH 02/18] python3-psutil: submit patch upstream Alexander Kanavin
2022-04-27  8:39 ` [PATCH 03/18] gnu-config: update to latest revision Alexander Kanavin
2022-04-27  8:39 ` [PATCH 04/18] go-helloworld: " Alexander Kanavin
2022-04-27  8:39 ` [PATCH 05/18] piglit: " Alexander Kanavin
2022-04-27  8:39 ` [PATCH 06/18] vulkan-samples: " Alexander Kanavin
2022-04-27  8:39 ` [PATCH 07/18] python3-typing-extensions: upgrade 3.10.0.0 -> 4.2.0 Alexander Kanavin
2022-04-27  8:39 ` [PATCH 08/18] python3-pyparsing: upgrade 3.0.7 -> 3.0.8 Alexander Kanavin
2022-04-27  8:40 ` [PATCH 09/18] glib: upgrade 2.72.0 -> 2.72.1 Alexander Kanavin
2022-04-27  8:40 ` [PATCH 10/18] go: update 1.18 -> 1.18.1 Alexander Kanavin
2022-04-28 16:22   ` [OE-core] " Steve Sakoman
2022-04-28 17:03     ` Khem Raj
2022-04-28 18:00       ` Steve Sakoman
2022-04-28 20:36         ` Khem Raj
2022-04-27  8:40 ` [PATCH 11/18] llvm: update 14.0.0 -> 14.0.1 Alexander Kanavin
2022-04-27  8:40 ` [PATCH 12/18] meson: update 0.61.3 -> 0.62.1 Alexander Kanavin
2022-04-27  8:40 ` [PATCH 13/18] valgrind: update 3.18.1 -> 3.19.0 Alexander Kanavin
2022-04-27 13:08   ` [OE-core] " Richard Purdie
2022-04-27 14:34     ` Alexander Kanavin
2022-04-27 14:37       ` Richard Purdie [this message]
2022-04-27  8:40 ` [PATCH 14/18] icu: update 70.1 -> 71.1 Alexander Kanavin
2022-04-27  8:40 ` [PATCH 15/18] libcap-ng: update 0.8.2 -> 0.8.3 Alexander Kanavin
2022-04-27  8:40 ` [PATCH 16/18] libgpg-error: 1.44 -> 1.45 Alexander Kanavin
2022-04-27  8:40 ` [PATCH 17/18] cmake: update 3.23.0 -> 3.23.1 Alexander Kanavin
2022-04-27  8:40 ` [PATCH 18/18] stress-ng: upgrade 0.13.12 -> 0.14.00 Alexander Kanavin
2022-05-05 13:57   ` [OE-core] " Luca Ceresoli
2022-05-05 15:18     ` Alexander Kanavin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d90f055950c3891d373d2fdec2358f902d4564de.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox