From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] libdrm: version bump 2.4.112 -> 2.4.113
Date: Fri, 11 Nov 2022 15:31:06 +0100 [thread overview]
Message-ID: <20221111143106.892228-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20221021104202.3131552-1-p.zabel@pengutronix.de>
Thanks, applied as 67fb039b0d858e442581d8279448d8af1ae82063.
Michael
[sent from post-receive hook]
On Fri, 11 Nov 2022 15:31:06 +0100, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Message-Id: <20221021104202.3131552-1-p.zabel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libdrm.make b/rules/libdrm.make
> index 262cd045dbc2..39ebe3d98211 100644
> --- a/rules/libdrm.make
> +++ b/rules/libdrm.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBDRM) += libdrm
> #
> # Paths and names
> #
> -LIBDRM_VERSION := 2.4.112
> -LIBDRM_MD5 := 2db7e05df012cab16d6c547317407ff2
> +LIBDRM_VERSION := 2.4.113
> +LIBDRM_MD5 := 34a4dcf7eaf0c771b3b0757b5fd5f803
> LIBDRM := libdrm-$(LIBDRM_VERSION)
> LIBDRM_SUFFIX := tar.xz
> LIBDRM_URL := http://dri.freedesktop.org/libdrm/$(LIBDRM).$(LIBDRM_SUFFIX)
> @@ -39,7 +39,6 @@ LIBDRM_BACKENDS-$(PTXCONF_LIBDRM_RADEON) += radeon
> LIBDRM_BACKENDS-$(PTXCONF_LIBDRM_AMDGPU) += amdgpu
> LIBDRM_BACKENDS-$(PTXCONF_LIBDRM_NOUVEAU) += nouveau
> LIBDRM_BACKENDS-$(PTXCONF_LIBDRM_FREEDRENO) += freedreno
> -LIBDRM_BACKENDS- += freedreno-kgsl
> LIBDRM_BACKENDSC-$(PTXCONF_LIBDRM_VMWGFX) += vmwgfx
> LIBDRM_BACKENDS-$(PTXCONF_LIBDRM_OMAP) += omap
> LIBDRM_BACKENDS-$(PTXCONF_LIBDRM_EXYNOS) += exynos
> @@ -58,12 +57,14 @@ LIBDRM_BACKENDSL-y += $(LIBDRM_BACKENDS-y)
> LIBDRM_CONF_TOOL := meson
> LIBDRM_CONF_OPT := \
> $(CROSS_MESON_USR) \
> - $(patsubst %,-D%=true,$(LIBDRM_BACKENDSC-y)) \
> - $(patsubst %,-D%=false,$(LIBDRM_BACKENDSC-)) \
> - -Dcairo-tests=false \
> - -Dman-pages=false \
> - -Dvalgrind=false \
> + $(patsubst %,-D%=enabled,$(LIBDRM_BACKENDSC-y)) \
> + $(patsubst %,-D%=disabled,$(LIBDRM_BACKENDSC-)) \
> + -Dcairo-tests=disabled \
> + -Dfreedreno-kgsl=false \
> + -Dman-pages=disabled \
> + -Dvalgrind=disabled \
> -Dinstall-test-programs=$(call ptx/truefalse, PTXCONF_LIBDRM_TESTS) \
> + -Dtests=true \
> -Dudev=true
>
>
prev parent reply other threads:[~2022-11-11 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 10:42 [ptxdist] [PATCH] " Philipp Zabel
2022-11-11 14:31 ` 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=20221111143106.892228-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--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