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.5 -> 2.1.5.1
Date: Fri, 17 Feb 2023 16:35:31 +0100 [thread overview]
Message-ID: <20230217153531.1224389-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230210144201.638281-1-christian.melki@t2data.com>
Thanks, applied as f4a008019dbb7805fc671a85d7dea36cbd229272.
Michael
[sent from post-receive hook]
On Fri, 17 Feb 2023 16:35:30 +0100, Christian Melki <christian.melki@t2data.com> wrote:
> Very minor bugfix release. Just a fix for assymetrical insn. set CPUs.
> (f.ex x86_64 Intels with P/E cores.)
> https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/2.1.5.1
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230210144201.638281-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 29cc563ef44d..88339db011d1 100644
> --- a/rules/libjpeg.make
> +++ b/rules/libjpeg.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBJPEG) += libjpeg
> #
> # Paths and names
> #
> -LIBJPEG_VERSION := 2.1.5
> -LIBJPEG_MD5 := 1c6e9f8550a82c6d4cd30b370c22a5fd
> +LIBJPEG_VERSION := 2.1.5.1
> +LIBJPEG_MD5 := aed60d4d776dd5cf00b5a01c609d50f7
> LIBJPEG_SUFFIX := tar.gz
> LIBJPEG := libjpeg-turbo-$(LIBJPEG_VERSION)
> LIBJPEG_TARBALL := $(LIBJPEG).$(LIBJPEG_SUFFIX)
prev parent reply other threads:[~2023-02-17 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 14:42 [ptxdist] [PATCH] " Christian Melki
2023-02-17 15:35 ` 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=20230217153531.1224389-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