From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: for-next updated to 9807b773dad4
Date: Fri, 9 Dec 2016 17:31:49 +1100 [thread overview]
Message-ID: <20161209063149.GP4219@dastard> (raw)
[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]
Hi folks.
The for-next branch of the xfs kernel repository at
git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git
has just been updated.
Ok, I was wrong, there were sufficient outstanding patches that I'd
missed to do another update before the 4.10 cycle. This should be
the last update now, honest! (Especially as the 4.10 merge window
will be abbreviated by Linus' xmas holiday schedule.)
-Dave.
The new head of the for-next branch is commit:
9807b773dad4 Merge branch 'xfs-4.10-misc-fixes-4' into for-next
New Commits:
Darrick J. Wong (1):
[b24a978c377b] xfs: use GPF_NOFS when allocating btree cursors
Dave Chinner (3):
[2291dab2c9d1] xfs: Always flush caches when integrity is required
[4cf4573d899c] xfs: deprecate barrier/nobarrier mount option
[9807b773dad4] Merge branch 'xfs-4.10-misc-fixes-4' into for-next
Eric Sandeen (2):
[2e1d23370e75] xfs: ignore leaf attr ichdr.count in verifier during log replay
[9875258ca7ab] xfs: nuke unused tracepoint definitions
Eryu Guan (1):
[0c187dc508d7] xfs: use xfs_vn_setattr_size to check on new size
Code Diffstat:
Documentation/filesystems/xfs.txt | 12 ++---
fs/xfs/libxfs/xfs_alloc_btree.c | 2 +-
fs/xfs/libxfs/xfs_attr_leaf.c | 8 ++-
fs/xfs/libxfs/xfs_bmap_btree.c | 2 +-
fs/xfs/libxfs/xfs_ialloc_btree.c | 2 +-
fs/xfs/xfs_buf.c | 3 +-
fs/xfs/xfs_file.c | 29 +++++-----
fs/xfs/xfs_iops.c | 2 +-
fs/xfs/xfs_log.c | 39 ++++++--------
fs/xfs/xfs_super.c | 25 +++++----
fs/xfs/xfs_trace.h | 109 --------------------------------------
11 files changed, 60 insertions(+), 173 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2016-12-09 6:32 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=20161209063149.GP4219@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@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