From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 5.16.2
Date: Wed, 16 Feb 2022 23:28:07 +0100 [thread overview]
Message-ID: <20220216222807.21681-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 5.16.2 have been released. This is a bugfix release.
Changelog:
* mkfs: fix detection of profile type for zoned mode when creating DUP
* build:
* add missing stub for zoned mode helper when zoned mode not enabled
* fix 64bit types on MIPS and PowerPC
* improved zoned mode support autodetection, for systems with existing
blkzone.h header but missing support for zone capacity
* other:
* doc updates
* test updates
Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
Shortlog:
David Sterba (6):
btrfs-progs: build: add stub definition for non-zoned build
btrfs-progs: build: improve autodetection of zoned mode
btrfs-progs: tests: add more configure options for build tests
btrfs-progs: tests: drop 32-on-64bit build support
btrfs-progs: update CHANGES for 5.16.2
Btrfs progs v5.16.2
Howard (1):
btrfs-progs: subvolume snapshot: added clarity how snapshot path is interprted
Johannes Thumshirn (1):
btrfs-progs: pass in block-group type to zoned_profile_supported
Josef Bacik (1):
btrfs-progs: sanity check global roots key.offset
Philip Guyton (1):
btrfs-progs: docs: update remaining non-zero dev stats -s option to -c
Rosen Penev (1):
btrfs-progs: fix 64-bit mips and powerpc types
dathide (1):
btrfs-progs: docs: remove incorrect statement about mkfs runtime features
jtagcat (1):
btrfs-progs: docs: clarify zstd level mapping
reply other threads:[~2022-02-16 22:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220216222807.21681-1-dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.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