From: Philipp Zabel <p.zabel@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 3/6] spirv-tools: version bump 2021.4 -> 1.3.204.0, separate spirv-headers
Date: Thu, 24 Feb 2022 17:14:47 +0100 [thread overview]
Message-ID: <2d3c333a085ec14bb46ea62ccf9e25d1fc4137d5.camel@pengutronix.de> (raw)
In-Reply-To: <20220224155639.micrh3hyqsfybdei@pengutronix.de>
On Do, 2022-02-24 at 16:56 +0100, Roland Hieber wrote:
[...]
> > --- a/rules/spirv-tools.make
> > +++ b/rules/spirv-tools.make
> > @@ -14,26 +14,25 @@ PACKAGES-$(PTXCONF_SPIRV_TOOLS) += spirv-tools
> > #
> > # Paths and names
> > #
> > -SPIRV_TOOLS_VERSION := 2021.4
> > -SPIRV_TOOLS_MD5 := bb36f699fcaca7362b983d75fa5a547b
> > +SPIRV_TOOLS_VERSION := 1.3.204.0
>
> Hmm, I wonder if this make problems with ipkg complaining about
> versions going backwards, or whether we need to care about this at
> all.
Good question, glslang has the same issue (and already had this happen
in the past [1] when tags were introduced).
[1] 37194316d01e ("glslang: version bump 2021-02-18-ge56beaee7368 -> 11.4.0")
regards
Philipp
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2022-02-24 16:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 10:17 [ptxdist] [PATCH 1/6] glslang: version bump 11.7.1 -> 1.3.204.0 Philipp Zabel
2022-02-23 10:17 ` [ptxdist] [PATCH 2/6] shaderc: version bump v2021.3 -> v2022.1 Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-23 10:17 ` [ptxdist] [PATCH 3/6] spirv-tools: version bump 2021.4 -> 1.3.204.0, separate spirv-headers Philipp Zabel
2022-02-24 15:56 ` Roland Hieber
2022-02-24 16:14 ` Philipp Zabel [this message]
2022-02-25 8:27 ` Michael Olbrich
2022-02-23 10:17 ` [ptxdist] [PATCH 4/6] vulkan-loader: version bump 1.2.198.1 -> 1.3.204.0 Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-23 10:17 ` [ptxdist] [PATCH 5/6] vulkan-tools: version bump 1.2.198.0 " Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-23 10:17 ` [ptxdist] [PATCH 6/6] vulkan-validationlayers: " Philipp Zabel
2022-02-28 12:09 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-02-24 15:54 ` [ptxdist] [PATCH 1/6] glslang: version bump 11.7.1 " Roland Hieber
2022-02-24 16:07 ` Philipp Zabel
2022-02-25 8:42 ` Michael Olbrich
2022-02-25 8:24 ` Michael Olbrich
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=2d3c333a085ec14bb46ea62ccf9e25d1fc4137d5.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=rhi@pengutronix.de \
/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