From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] fuse3: version bump 3.17.4 -> 3.18.3
Date: Tue, 6 Oct 2026 09:01:35 +0200 [thread overview]
Message-ID: <20261006070135.2793028-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260929074925.1150353-1-s.pueschel@pengutronix.de>
Thanks, applied as 3ebb5cd364e072c38b3d21e6272db0cbbac1b0ef.
Michael
[sent from post-receive hook]
On Tue, 06 Oct 2026 09:01:35 +0200, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> Disable all new options. While uring support is enabled by default and
> may improve the performance, it would add dependencies to liburing and numa.
>
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20260929074925.1150353-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/fuse3.make b/rules/fuse3.make
> index e234db7817e1..d7be4e322d87 100644
> --- a/rules/fuse3.make
> +++ b/rules/fuse3.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_FUSE3) += fuse3
> #
> # Paths and names
> #
> -FUSE3_VERSION := 3.17.4
> -FUSE3_SHA256 := df9e40ae927b73dc702d0bce7925c0c618af47ad0b13204fbf2be66e54d8528b
> +FUSE3_VERSION := 3.18.3
> +FUSE3_SHA256 := bcd19582c5e30f7fe45dd86a5540e998590aa01903afc7ebcbeea6c8ac5421ee
> FUSE3 := fuse-$(FUSE3_VERSION)
> FUSE3_SUFFIX := tar.gz
> FUSE3_URL := https://github.com/libfuse/libfuse/releases/download/$(FUSE3)/$(FUSE3).$(FUSE3_SUFFIX)
> @@ -39,6 +39,9 @@ FUSE3_CONF_OPT := \
> $(CROSS_MESON_USR) \
> -Ddisable-libc-symbol-version=true \
> -Ddisable-mtab=true \
> + -Denable-custom-io=false \
> + -Denable-io-uring=false \
> + -Denable-usdt=false \
> -Dexamples=false \
> -Dtests=false \
> -Dudevrulesdir=/usr/lib/udev/rules.d \
prev parent reply other threads:[~2026-10-06 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 7:49 [ptxdist] [PATCH] " Sven Püschel
2026-10-06 7:01 ` 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=20261006070135.2793028-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