From: Peter Kjellerstedt <pkj@axis.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH] mesa-libclc: Correct the license
Date: Wed, 9 Sep 2026 19:36:09 +0200 [thread overview]
Message-ID: <20260909173609.1197773-1-pkj@axis.com> (raw)
Use "Apache-2.0 WITH LLVM-exception" now that license exceptions are
properly supported.
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
---
meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb b/meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb
index c93b5b9d9d..cad78f67f5 100644
--- a/meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb
+++ b/meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb
@@ -1,7 +1,7 @@
SUMMARY = "Mesa fork of libclc: Implementation of the library requirements of the OpenCL C programming language."
HOMEPAGE = "https://gitlab.freedesktop.org/karolherbst/mesa-libclc/"
SECTION = "devel"
-LICENSE = "Apache-2.0-with-LLVM-exception"
+LICENSE = "Apache-2.0 WITH LLVM-exception"
LIC_FILES_CHKSUM = "file://LICENSE.TXT;md5=7cc795f6cbb2d801d84336b83c8017db"
SRC_URI = "git://gitlab.freedesktop.org/karolherbst/mesa-libclc.git;protocol=https;branch=llvm_22"
reply other threads:[~2026-09-09 17:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260909173609.1197773-1-pkj@axis.com \
--to=pkj@axis.com \
--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