All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Petr Vorel <petr.vorel@gmail.com>,
	 openembedded-core@lists.openembedded.org
Cc: Khem Raj <raj.khem@gmail.com>,
	Tim Orling <tim.orling@konsulko.com>,
	Hui Min Mina Chou <minachou@andestech.com>
Subject: Re: [PATCH 1/1] ltp: Update to 20250130
Date: Sun, 02 Feb 2025 06:33:02 +0000	[thread overview]
Message-ID: <166c73cfa10449a1163cefae2879ca881f3b42f9.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250131225444.1144932-1-petr.vorel@gmail.com>

Hi Petr,

Thanks for the patch.

On Fri, 2025-01-31 at 23:54 +0100, Petr Vorel wrote:
> Removed 0001-sched_attr-Do-not-define-for-glibc-2.41.patch
> (accepted upstream)
> 
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> Hi all,
> 
> could please anybody test this patch? (I'm an LTP upstream developer
> with very little Yocto / openembedded knowledge).
> 
> Would it be possible also to test if 0001-Add-__clear_cache-
> declaration-for-clang.patch
> is still needed? As Cyril noted at [1], it sounds like clang bug
> (__clear_cache() is a pre-defined function and as such the signature
> should be part of the compiler).
> 
> @Tim any change your kirk recipe is merged upstream?
> 
> Kind regards,
> Petr
> 
> [1] https://lore.kernel.org/ltp/Zmg9WZ1TitB7D_RC@yuki/
> [2] https://git.yoctoproject.org/poky-contrib/log/?h=timo/kirk

I ran it through our automated testing and whilst the main tests ran
ok, it failed on musl:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/932/steps/11/logs/stdio
https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/948/steps/11/logs/stdio

Cheers,

Richard





  reply	other threads:[~2025-02-02  6:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 22:54 [PATCH 1/1] ltp: Update to 20250130 Petr Vorel
2025-02-02  6:33 ` Richard Purdie [this message]
2025-02-02 12:22   ` Petr Vorel

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=166c73cfa10449a1163cefae2879ca881f3b42f9.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=minachou@andestech.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=petr.vorel@gmail.com \
    --cc=raj.khem@gmail.com \
    --cc=tim.orling@konsulko.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.