From: Jose Quaresma <quaresma.jose@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Ross Burton <Ross.Burton@arm.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/3] vulkan-headers: upgrade to 1.3.249
Date: Wed, 3 May 2023 11:02:16 +0100 [thread overview]
Message-ID: <CANPvuR=Fb7R8cced69NNXTqVRqEAMBvEPk+8qAU6RLzGGmqyUA@mail.gmail.com> (raw)
In-Reply-To: <CANNYZj-eVO3_KuvE27t4Y_bsRUuyokMKkhbAKNa-0w+21oBP2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1622 bytes --]
Hi,
Alexander Kanavin <alex.kanavin@gmail.com> escreveu no dia quarta,
3/05/2023 à(s) 09:47:
> On Wed, 3 May 2023 at 10:39, Ross Burton <Ross.Burton@arm.com> wrote:
> > > Please respect the upstream version check; vulkan should be updated to
> > > sdk-x.y.z versions, which currently means 1.3.243.
> >
> > If that’s a policy and not just because of historical branch structure,
> please add a comment explaining this to the recipes.
>
> Vulkan items need to be updated in lockstep with things like glslang,
> and those only get tags for vulkan sdk releases:
> https://github.com/KhronosGroup/glslang/tags
>
>
The spirv-headers and the spirv-tools usually also go together with the
vulkan update.
https://github.com/KhronosGroup/SPIRV-Headers/tags
https://github.com/KhronosGroup/SPIRV-Tools/tags
Jose
Also, there's less upgrade churn that way, as we can skip over many
> intermediate development versions that happen weekly or more often.
>
> I'll add a comment, but checking the version with devtool and then
> performing the upgrade with it would've done the correct thing.
>
> Alex
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#180789):
> https://lists.openembedded.org/g/openembedded-core/message/180789
> Mute This Topic: https://lists.openembedded.org/mt/98647309/5052612
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> quaresma.jose@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
--
Best regards,
José Quaresma
[-- Attachment #2: Type: text/html, Size: 3080 bytes --]
prev parent reply other threads:[~2023-05-03 10:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 19:59 [PATCH 1/3] vulkan-headers: upgrade to 1.3.249 Ross Burton
2023-05-02 19:59 ` [PATCH 2/3] vulkan-loader: " Ross Burton
2023-05-02 19:59 ` [PATCH 3/3] vulkan-tools: " Ross Burton
2023-05-03 8:37 ` [OE-core] [PATCH 1/3] vulkan-headers: " Alexander Kanavin
2023-05-03 8:39 ` Ross Burton
2023-05-03 8:47 ` Alexander Kanavin
2023-05-03 10:02 ` Jose Quaresma [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='CANPvuR=Fb7R8cced69NNXTqVRqEAMBvEPk+8qAU6RLzGGmqyUA@mail.gmail.com' \
--to=quaresma.jose@gmail.com \
--cc=Ross.Burton@arm.com \
--cc=alex.kanavin@gmail.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 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.