From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libjpeg: Version bump. 2.1.4 -> 2.1.5.
Date: Fri, 10 Feb 2023 15:17:08 +0100 [thread overview]
Message-ID: <20230210141708.3533058-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230202124608.1164456-1-christian.melki@t2data.com>
Thanks, applied as 8308034c10107fc6449c7f904fe2a168bcdc9d8b.
Michael
[sent from post-receive hook]
On Fri, 10 Feb 2023 15:17:07 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Bugfix release. Nothing overly relevant to most users.
> https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/2.1.5
>
> * License file year changes. Fix hash.
> * Add altivec optimizations since ptxdist now supports it.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230202124608.1164456-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libjpeg.make b/rules/libjpeg.make
> index 60125b77d145..29cc563ef44d 100644
> --- a/rules/libjpeg.make
> +++ b/rules/libjpeg.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBJPEG) += libjpeg
> #
> # Paths and names
> #
> -LIBJPEG_VERSION := 2.1.4
> -LIBJPEG_MD5 := 3241b54016c445e5d8f0ebb0ad9294ed
> +LIBJPEG_VERSION := 2.1.5
> +LIBJPEG_MD5 := 1c6e9f8550a82c6d4cd30b370c22a5fd
> LIBJPEG_SUFFIX := tar.gz
> LIBJPEG := libjpeg-turbo-$(LIBJPEG_VERSION)
> LIBJPEG_TARBALL := $(LIBJPEG).$(LIBJPEG_SUFFIX)
> @@ -26,7 +26,7 @@ LIBJPEG_SOURCE := $(SRCDIR)/$(LIBJPEG_TARBALL)
> LIBJPEG_DIR := $(BUILDDIR)/$(LIBJPEG)
> LIBJPEG_LICENSE := IJG, BSD-3-Clause, Zlib
> LIBJPEG_LICENSE_FILES := \
> - file://LICENSE.md;md5=a75feaa2de6d8942f50d412241fca1f1 \
> + file://LICENSE.md;md5=2a8e0d8226a102f07ab63ed7fd6ce155 \
> file://README.ijg;startline=112;endline=174;md5=9fcb5339d9de46b31309aeef52d7deb1 \
> file://simd/nasm/jsimdext.inc;startline=13;endline=28;md5=839b9ed7df5168976efc071bee29a76e
>
> @@ -42,6 +42,9 @@ endif
> ifdef PTXCONF_ARCH_ARM_NEON
> LIBJPEG_SIMD := y
> endif
> +ifdef PTXCONF_ARCH_PPC_ALTIVEC
> +LIBJPEG_SIMD := y
> +endif
>
> LIBJPEG_CONF_TOOL := cmake
> LIBJPEG_CONF_OPT := \
prev parent reply other threads:[~2023-02-10 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 12:46 [ptxdist] [PATCH] " Christian Melki
2023-02-10 14:17 ` Michael Olbrich [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=20230210141708.3533058-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@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