From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: clm@fb.com
Subject: Btrfs progs pre-release 4.8.1-rc1
Date: Fri, 7 Oct 2016 14:26:51 +0200 [thread overview]
Message-ID: <20161007122651.5125-1-dsterba@suse.com> (raw)
Hi,
another pre-release, just in case. I did a lot of build tests [1] and
automated a few things so the build failures should not happen again.
ETA for the release is on Sunday (2016-10-09). Please test and report any new
problems.
Changes since 4.8:
- 32bit build works
- build without backtrace support fixed
[1]
build tests on arches: arm, aarch64, ppc, ppc64, ppc64le, i586, x86_64
32/64 build on x86_64 (X) default, static (X) gcc 4.8.5, gcc 5.41, gcc 6.2.1
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 (10):
btrfs-progs: build: add explicit option separator to rm commands
btrfs-progs: ioctl: pack structures
btrfs-progs: ioctl: add 32bit compat for SET_RECEIVED_SUBVOL
btrfs-progs: ioctl: add 64bit compat for SEND
btrfs-progs: tests: make the ioctl-test actually useful
btrfs-progs: tests: add script to help build coverage
btrfs-progs: fix printf format of sizeof on 32bit build
btrfs-progs: test: add default ioctl-test build
btrfs-progs: update CHANGES for v4.8.1
Btrfs progs v4.8.1-rc1
Qu Wenruo (1):
btrfs-progs: Fix warning_trace compile error if backtrace is disabled
next reply other threads:[~2016-10-07 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 12:26 David Sterba [this message]
2016-10-07 19:57 ` Btrfs progs pre-release 4.8.1-rc1 Justin Maggard
2016-10-09 20:40 ` David Sterba
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=20161007122651.5125-1-dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.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