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. 3.0.4 -> 3.1.0
Date: Thu, 16 Jan 2025 17:09:32 +0100 [thread overview]
Message-ID: <20250116160932.426937-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20241217200827.2650279-1-christian.melki@t2data.com>
Thanks, applied as f366efe5e385ed6f3679929524435bca5a505900.
Michael
[sent from post-receive hook]
On Thu, 16 Jan 2025 17:09:32 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Probably the biggest change is the addition of lossless JPEGs.
> https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/3.1.0
> https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/3.0.90
>
> * LICENSE.md5 changed, copyright year updates.
>
> * README.ijg changed, minor adjustments.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20241217200827.2650279-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 f6e4957cac4c..c4ea675ae89f 100644
> --- a/rules/libjpeg.make
> +++ b/rules/libjpeg.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBJPEG) += libjpeg
> #
> # Paths and names
> #
> -LIBJPEG_VERSION := 3.0.4
> -LIBJPEG_MD5 := a816d48923e86c963c26d00e877f7db7
> +LIBJPEG_VERSION := 3.1.0
> +LIBJPEG_MD5 := 1695d39ba38a9593f4107722f3459fe0
> LIBJPEG_SUFFIX := tar.gz
> LIBJPEG := libjpeg-turbo-$(LIBJPEG_VERSION)
> LIBJPEG_URL := https://github.com/libjpeg-turbo/libjpeg-turbo/archive/refs/tags/$(LIBJPEG_VERSION).$(LIBJPEG_SUFFIX)
> @@ -25,8 +25,8 @@ LIBJPEG_SOURCE := $(SRCDIR)/$(LIBJPEG).$(LIBJPEG_SUFFIX)
> LIBJPEG_DIR := $(BUILDDIR)/$(LIBJPEG)
> LIBJPEG_LICENSE := IJG AND BSD-3-Clause
> LIBJPEG_LICENSE_FILES := \
> - file://LICENSE.md;md5=2badff2388880cc27e58977d8bc1d494 \
> - file://README.ijg;startline=112;endline=174;md5=9fcb5339d9de46b31309aeef52d7deb1 \
> + file://LICENSE.md;md5=023c2e8942020502d6ea709e2a5453f7 \
> + file://README.ijg;startline=113;endline=164;md5=89d5b942e03050d117f34e50b49c2c61 \
> file://simd/nasm/jsimdext.inc;startline=13;endline=28;md5=100ad877b6a14ec137afd49a6e109624
>
> # ----------------------------------------------------------------------------
prev parent reply other threads:[~2025-01-16 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 20:08 [ptxdist] [PATCH] " Christian Melki
2025-01-16 16:09 ` 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=20250116160932.426937-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