From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] dav1d: version bump 1.5.1 -> 1.5.4
Date: Fri, 13 Nov 2026 09:38:50 +0100 [thread overview]
Message-ID: <20261113083850.1378591-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20261020135103.3450184-1-s.pueschel@pengutronix.de>
Thanks, applied as 8e4f60bbb7ecf77cde23c14422a1888902e177e0.
Michael
[sent from post-receive hook]
On Fri, 13 Nov 2026 09:38:50 +0100, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> primarily speed optimizations
> https://code.videolan.org/videolan/dav1d/-/releases/1.5.2
> https://code.videolan.org/videolan/dav1d/-/releases/1.5.3
> https://code.videolan.org/videolan/dav1d/-/releases/1.5.4
>
> The COPYING hash changed due to a year change (2019 -> 2025).
>
> Adjusted the build options to match the ordering of the
> configure_helper.py script.
>
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20261020135103.3450184-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/dav1d.make b/rules/dav1d.make
> index 8f5956f0554e..552a43e54d88 100644
> --- a/rules/dav1d.make
> +++ b/rules/dav1d.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_DAV1D) += dav1d
> #
> # Paths and names
> #
> -DAV1D_VERSION := 1.5.1
> -DAV1D_SHA256 := 4eddffd108f098e307b93c9da57b6125224dc5877b1b3d157b31be6ae8f1f093
> +DAV1D_VERSION := 1.5.4
> +DAV1D_SHA256 := 2abfb0c89212e6e4733a54e0ae509ec00a5b845a6360946f918806e14aedb011
> DAV1D := dav1d-$(DAV1D_VERSION)
> DAV1D_SUFFIX := tar.bz2
> DAV1D_URL := https://code.videolan.org/videolan/dav1d/-/archive/$(DAV1D_VERSION)/$(DAV1D).$(DAV1D_SUFFIX)
> @@ -23,7 +23,7 @@ DAV1D_SOURCE := $(SRCDIR)/$(DAV1D).$(DAV1D_SUFFIX)
> DAV1D_DIR := $(BUILDDIR)/$(DAV1D)
> DAV1D_LICENSE := BSD-2-Clause
> DAV1D_LICENSE_FILES := \
> - file://COPYING;md5=c8055cfe7548dfdaa3a6dc45d8793669
> + file://COPYING;md5=48d9210a87a24f62609b5a4f777d8dfe
>
> # ----------------------------------------------------------------------------
> # Prepare
> @@ -35,10 +35,10 @@ DAV1D_LICENSE_FILES := \
> DAV1D_CONF_TOOL := meson
> DAV1D_CONF_OPT := \
> $(CROSS_MESON_USR) \
> - -Denable_tools=false \
> + -Denable_docs=false \
> -Denable_examples=false \
> -Denable_tests=false \
> - -Denable_docs=false
> + -Denable_tools=false
>
> # ----------------------------------------------------------------------------
> # Target-Install
prev parent reply other threads:[~2026-11-13 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 13:51 [ptxdist] [PATCH] " Sven Püschel
2026-11-13 8:38 ` 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=20261113083850.1378591-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=s.pueschel@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