Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: alex.kanavin@gmail.com, Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: dbaryshkov@gmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] mesa: upgrade 24.0.7 -> 24.3.4
Date: Mon, 3 Feb 2025 12:17:28 +0100	[thread overview]
Message-ID: <b407c45e-030a-4707-be56-0f5ff1cde46d@cherry.de> (raw)
In-Reply-To: <CANNYZj-iMjQnJ6OZDDGJ6ofeNEQVmvby9cSzOrQh8GBcVVXtmg@mail.gmail.com>



On 2/3/25 12:14 PM, Alexander Kanavin via lists.openembedded.org wrote:
> On Sat, 1 Feb 2025 at 12:37, Dmitry Baryshkov
> <dmitry.baryshkov@linaro.org> wrote:
>>> How was this tested? For me it fails immediately with the same error
>>> as the previous update attempts:
>>
>> Yes, I forgot about the Intel world, I was testing on ARM & ARM64.
> 
> Please remember to try at least the basic poky config (which is qemux86-64).
> 
>>> Basically, mesa updates are blocked until clang lands in core. If you
>>> want new mesa, please do help out.
>>
>> Is there any work in progress? The latest attempt I see was made in
>> November.
> 
> RP has recently reviewed the patches, so you need to find the review.
> 

https://lore.kernel.org/openembedded-core/20241105184540.3450302-1-raj.khem@gmail.com/ 
for the series.

Cheers,
Quentin


      reply	other threads:[~2025-02-03 11:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 12:35 [PATCH] mesa: upgrade 24.0.7 -> 24.3.4 Dmitry Baryshkov
2025-01-31 12:59 ` [OE-core] " Alexander Kanavin
2025-01-31 13:17   ` Quentin Schulz
2025-01-31 16:34     ` Markus Volk
2025-02-01 11:37   ` Dmitry Baryshkov
2025-02-03  5:17     ` Böszörményi Zoltán
2025-02-03 11:17       ` Alexander Kanavin
2025-02-07 19:05         ` Markus Volk
2025-02-03 11:14     ` Alexander Kanavin
2025-02-03 11:17       ` Quentin Schulz [this message]

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=b407c45e-030a-4707-be56-0f5ff1cde46d@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=alex.kanavin@gmail.com \
    --cc=dbaryshkov@gmail.com \
    --cc=dmitry.baryshkov@linaro.org \
    --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