Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <zboszor@gmail.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/3] mesa-libclc: New recipe for forking libclc for Rusticl purposes in Mesa
Date: Sun, 19 Jul 2026 08:26:08 +0200	[thread overview]
Message-ID: <DK2C0Z9DDTDG.OTLWJC41N5TD@bootlin.com> (raw)
In-Reply-To: <20260718050502.62359-2-zboszor@gmail.com>

On Sat Jul 18, 2026 at 7:05 AM CEST, Zoltan Boszormenyi via lists.openembedded.org wrote:
> See the reasoning and discussion at
> https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/43020
>
> TL;DR: LLVM constantly introduces breaking changes that cause
> regressions for running OpenCL CTS with Rusticl and finally
> Karol Herbst had enough.
>
> This fork is from the LLVM 22 version of libclc and contains the
> necessary fixes to make Rusticl pass OpenCL CTS.
>
> Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
> ---

Hi Zoltán,

Thanks for your patch. Please keep in mind you need to add an entry in
meta/conf/distro/include/maintainers.inc.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-07-19  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-18  5:05 [PATCH 1/3] mesa: Upgrade to 26.1.5 Zoltán Böszörményi
2026-07-18  5:05 ` [PATCH 2/3] mesa-libclc: New recipe for forking libclc for Rusticl purposes in Mesa Zoltán Böszörményi
2026-07-19  6:26   ` Mathieu Dubois-Briand [this message]
2026-07-18  5:05 ` [PATCH 3/3] mesa, mesa-tools-native: Use mesa-libclc Zoltán Böszörményi

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=DK2C0Z9DDTDG.OTLWJC41N5TD@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=zboszor@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox