From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: jmaggard10@gmail.com, clm@fb.com
Subject: Btrfs progs pre-release 4.8.1-rc2
Date: Mon, 10 Oct 2016 10:38:02 +0200 [thread overview]
Message-ID: <20161010083802.9420-1-dsterba@suse.com> (raw)
Hi,
another pre-release. The problem with ioctl on 32bit ARM that Justin reported
shows we have to be more careful with the changes to ioctl structures. The
build size checks are now optional (make D=bcheck to enable) and the patches to
add packing, alignment or alternate structures are left out.
ETA for 4.8.1 is tomorrow.
Changes since 4.8:
- 32bit build works
- build without backtrace support fixed
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 explicit option separator to rm commands
btrfs-progs: tests: add script to help build coverage
btrfs-progs: fix printf format of sizeof on 32bit build
btrfs-progs: ioctl: make build-time structure size checks optional
btrfs-progs: update CHANGES for v4.8.1
Btrfs progs v4.8.1-rc2
Qu Wenruo (1):
btrfs-progs: Fix warning_trace compile error if backtrace is disabled
reply other threads:[~2016-10-10 9:53 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=20161010083802.9420-1-dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.com \
--cc=jmaggard10@gmail.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;
as well as URLs for NNTP newsgroup(s).