From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-core@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH] mesa: upgrade 22.1.6 -> 22.1.7
Date: Mon, 5 Sep 2022 17:03:19 +0800 [thread overview]
Message-ID: <1662368601-32265-3-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1662368601-32265-1-git-send-email-wangmy@fujitsu.com>
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
.../mesa/{mesa-gl_22.1.6.bb => mesa-gl_22.1.7.bb} | 0
meta/recipes-graphics/mesa/mesa.inc | 2 +-
meta/recipes-graphics/mesa/{mesa_22.1.6.bb => mesa_22.1.7.bb} | 0
3 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/mesa/{mesa-gl_22.1.6.bb => mesa-gl_22.1.7.bb} (100%)
rename meta/recipes-graphics/mesa/{mesa_22.1.6.bb => mesa_22.1.7.bb} (100%)
diff --git a/meta/recipes-graphics/mesa/mesa-gl_22.1.6.bb b/meta/recipes-graphics/mesa/mesa-gl_22.1.7.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa-gl_22.1.6.bb
rename to meta/recipes-graphics/mesa/mesa-gl_22.1.7.bb
diff --git a/meta/recipes-graphics/mesa/mesa.inc b/meta/recipes-graphics/mesa/mesa.inc
index ea7ed4fd27..729c466554 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -25,7 +25,7 @@ SRC_URI = "https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
file://0001-nir-nir_opt_move-fix-ALWAYS_INLINE-compiler-error.patch \
"
-SRC_URI[sha256sum] = "22ced061eb9adab8ea35368246c1995c09723f3f71653cd5050c5cec376e671a"
+SRC_URI[sha256sum] = "da838eb2cf11d0e08d0e9944f6bd4d96987fdc59ea2856f8c70a31a82b355d89"
UPSTREAM_CHECK_GITTAGREGEX = "mesa-(?P<pver>\d+(\.\d+)+)"
diff --git a/meta/recipes-graphics/mesa/mesa_22.1.6.bb b/meta/recipes-graphics/mesa/mesa_22.1.7.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa_22.1.6.bb
rename to meta/recipes-graphics/mesa/mesa_22.1.7.bb
--
2.25.1
next prev parent reply other threads:[~2022-09-05 9:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 9:03 [OE-core] [PATCH] cracklib: upgrade 2.9.7 -> 2.9.8 Wang Mingyu
2022-09-05 9:03 ` [OE-core] [PATCH] kmscube: upgrade to latest revision Wang Mingyu
2022-09-05 9:03 ` Wang Mingyu [this message]
2022-09-05 9:03 ` [OE-core] [PATCH] piglit: " Wang Mingyu
2022-09-05 9:03 ` [OE-core] [PATCH] python3-dtschema: upgrade 2022.8.1 -> 2022.8.3 Wang Mingyu
-- strict thread matches above, loose matches on Subject: below --
2022-08-30 4:11 [OE-core] [PATCH] lttng-tools: upgrade 2.13.7 -> 2.13.8 Wang Mingyu
2022-08-30 4:11 ` [OE-core] [PATCH] mesa: upgrade 22.1.6 -> 22.1.7 Wang Mingyu
2022-08-30 20:16 ` Alexandre Belloni
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=1662368601-32265-3-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.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