From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libqmi: Version bump. 1.34.0 -> 1.36.0
Date: Fri, 9 May 2025 09:25:04 +0200 [thread overview]
Message-ID: <20250509072504.2679104-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20250410174046.3068504-1-christian.melki@t2data.com>
Thanks, applied as 0aaf18309c9951fd9bf9cb9400928e6c104e19f1.
Michael
[sent from post-receive hook]
On Fri, 09 May 2025 09:25:04 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Long due.
> https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/blob/qmi-1-36/NEWS
>
> * Rearrange options and add define a new one.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20250410174046.3068504-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libqmi.make b/rules/libqmi.make
> index 2cc6695cb061..f6017e53769c 100644
> --- a/rules/libqmi.make
> +++ b/rules/libqmi.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBQMI) += libqmi
> #
> # Paths and names
> #
> -LIBQMI_VERSION := 1.34.0
> -LIBQMI_MD5 := 677b5d1ab763a7b7285b82d1798ff93d
> +LIBQMI_VERSION := 1.36.0
> +LIBQMI_MD5 := e140fa38a1def3038af891c8f15b705b
> LIBQMI := libqmi-$(LIBQMI_VERSION)
> LIBQMI_SUFFIX := tar.bz2
> LIBQMI_URL := https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/archive/$(LIBQMI_VERSION)/$(LIBQMI).$(LIBQMI_SUFFIX)
> @@ -36,18 +36,19 @@ LIBQMI_LICENSE_FILES := \
> LIBQMI_CONF_TOOL := meson
> LIBQMI_CONF_OPT := \
> $(CROSS_MESON_USR) \
> - -Dfirmware_update=$(call ptx/truefalse, PTXCONF_LIBQMI_FIRMWARE_UPDATE) \
> + -Dbash_completion=false \
> -Dcollection=full \
> + -Dfirmware_update=$(call ptx/truefalse, PTXCONF_LIBQMI_FIRMWARE_UPDATE) \
> + -Dfuzzer=false \
> + -Dgtk_doc=false \
> + -Dintrospection=false \
> + -Dman=false \
> -Dmbim_qmux=$(call ptx/truefalse, PTXCONF_LIBQMI_MBIM_QMUX) \
> -Dmm_runtime_check=false \
> -Dqrtr=false \
> -Drmnet=false \
> -Dudev=false \
> - -Dudevdir=/usr/lib/udev \
> - -Dintrospection=false \
> - -Dgtk_doc=false \
> - -Dman=false \
> - -Dbash_completion=false
> + -Dudevdir=/usr/lib/udev
>
> # ----------------------------------------------------------------------------
> # Target-Install
prev parent reply other threads:[~2025-05-09 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 17:40 [ptxdist] [PATCH] " Christian Melki
2025-05-09 7:25 ` 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=20250509072504.2679104-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