mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
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.1.1 -> 3.1.2
Date: Mon,  8 Sep 2025 09:24:19 +0200	[thread overview]
Message-ID: <20250908072419.3510099-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250904181723.862768-1-christian.melki@t2data.com>

Thanks, applied as 392d78d70bb7856caaaeb2a1eb08403d5c58aeee.

Michael

[sent from post-receive hook]

On Mon, 08 Sep 2025 09:24:19 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> No big changes.
> https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/3.1.2
> 
> * License file changed, copyright year updates.
> 
> * Pin down options.
> 
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250904181723.862768-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 93c730727787..ca9c0a70e05e 100644
> --- a/rules/libjpeg.make
> +++ b/rules/libjpeg.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBJPEG) += libjpeg
>  #
>  # Paths and names
>  #
> -LIBJPEG_VERSION	:= 3.1.1
> -LIBJPEG_MD5	:= 4cc83d985db61e64bfa352388bb447ec
> +LIBJPEG_VERSION	:= 3.1.2
> +LIBJPEG_MD5	:= 2446ea45eb280ed785b265bd444f0c75
>  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,7 +25,7 @@ LIBJPEG_SOURCE	:= $(SRCDIR)/$(LIBJPEG).$(LIBJPEG_SUFFIX)
>  LIBJPEG_DIR	:= $(BUILDDIR)/$(LIBJPEG)
>  LIBJPEG_LICENSE	:= IJG AND BSD-3-Clause
>  LIBJPEG_LICENSE_FILES := \
> -	file://LICENSE.md;md5=023c2e8942020502d6ea709e2a5453f7 \
> +	file://LICENSE.md;md5=52fddabc7e8e79233150ebda95c3fc1f \
>  	file://README.ijg;startline=113;endline=164;md5=89d5b942e03050d117f34e50b49c2c61 \
>  	file://simd/nasm/jsimdext.inc;startline=13;endline=28;md5=100ad877b6a14ec137afd49a6e109624
>  
> @@ -59,6 +59,8 @@ LIBJPEG_CONF_OPT := \
>  	-DWITH_JPEG7=ON \
>  	-DWITH_JPEG8=ON \
>  	-DWITH_SIMD=$(call ptx/onoff,LIBJPEG_SIMD) \
> +	-DWITH_TESTS=OFF \
> +	-DWITH_TOOLS=ON \
>  	-DWITH_TURBOJPEG=$(call ptx/onoff,PTXCONF_LIBJPEG_TURBO)
>  
>  # ----------------------------------------------------------------------------



      reply	other threads:[~2025-09-08  7:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 18:17 [ptxdist] [PATCH] " Christian Melki
2025-09-08  7:24 ` 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=20250908072419.3510099-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