Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Wang Mingyu < wangmy@fujitsu.com>
To: openembedded-core@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [OE-core] [PATCH 04/16] btrfs-tools: upgrade 6.19.1 -> 7.0
Date: Wed, 10 Jun 2026 17:49:19 +0800	[thread overview]
Message-ID: <20260610094932.2264-4-wangmy@fujitsu.com> (raw)
In-Reply-To: <20260610094932.2264-1-wangmy@fujitsu.com>

From: Wang Mingyu <wangmy@fujitsu.com>

Changelog:
===========
- btrfstune: add ability to do offline conversion to the remap tree
  (experimental feature)
- mkfs: add hole detection when precalculating size for --rootdir
- fixes: recognize fs-verity tree items in various tools (check)
- enable PCLMUL implementation on Musl (previously using SSE 4.2 at best)
- help format changed to be in line with common packages like util-linux
- reject writes to filesystem during check/btrfstune in case there's pending
  state of device replace or balance
- other:
  build ARM64 static binaries (attached to GH release) backward compatibility level is 'archv8-a'
  CI updates
  documentation updates

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 .../btrfs-tools/{btrfs-tools_6.19.1.bb => btrfs-tools_7.0.bb}   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_6.19.1.bb => btrfs-tools_7.0.bb} (98%)

diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.19.1.bb b/meta/recipes-devtools/btrfs-tools/btrfs-tools_7.0.bb
similarity index 98%
rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_6.19.1.bb
rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_7.0.bb
index dee1270fa0..72b5575703 100644
--- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.19.1.bb
+++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_7.0.bb
@@ -18,7 +18,7 @@ DEPENDS = "util-linux zlib"
 SRC_URI = "git://github.com/kdave/btrfs-progs.git;branch=master;protocol=https;tag=v${PV} \
            file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
            "
-SRCREV = "fa79dbea32d39ac0ae41a88a079013c7ad2a8a58"
+SRCREV = "9c5987432906daebde23f9703c0f6f90c35fa9da"
 
 PACKAGECONFIG ??= " \
     programs \
-- 
2.43.0



  parent reply	other threads:[~2026-06-10  9:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10  9:49 [OE-core] [PATCH 01/16] alsa-lib: upgrade 1.2.15.3 -> 1.2.16 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 02/16] alsa-utils: upgrade 1.2.15.2 " Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 03/16] barebox-tools: upgrade 2026.04.0 -> 2026.06.0 Wang Mingyu
2026-06-10  9:49 ` Wang Mingyu [this message]
2026-06-10  9:49 ` [OE-core] [PATCH 05/16] dos2unix: upgrade 7.5.5 -> 7.5.6 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 06/16] dropbear: upgrade 2025.89 -> 2026.91 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 07/16] fastfloat: upgrade 8.2.5 -> 8.2.8 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 08/16] file: upgrade 5.47 -> 5.48 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 09/16] fontconfig: upgrade 2.17.1 -> 2.18.1 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 10/16] ghostscript: upgrade 10.07.0 -> 10.07.1 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 11/16] gpgme: upgrade 2.0.1 -> 2.1.0 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 12/16] harfbuzz: upgrade 14.2.0 -> 14.2.1 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 13/16] hwdata: upgrade 0.406 -> 0.408 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 14/16] kbd: upgrade 2.9.0 -> 2.10.0 Wang Mingyu
2026-06-10  9:49 ` [OE-core] [PATCH 15/16] mesa: upgrade 26.0.6 -> 26.1.2,26.0.6 -> 26.1.2 Wang Mingyu
2026-06-11  5:14   ` Mathieu Dubois-Briand
2026-06-12  9:26     ` Mingyu Wang (Fujitsu)
2026-06-10  9:49 ` [OE-core] [PATCH 16/16] sbom-cve-check-update-nvd-native: upgrade 2026.05.07-000006 -> 2026.06.09-000006 Wang Mingyu

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=20260610094932.2264-4-wangmy@fujitsu.com \
    --to=wangmy@fujitsu.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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