From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch updated to 2cdb958
Date: Wed, 16 Mar 2016 07:39:08 +1100 [thread overview]
Message-ID: <20160315203908.GE11812@dastard> (raw)
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. This is the last update for the 4.6 merge
window - after it has sat in linux-next for a couple of days I'll
tag it and ask Linus to pull.
The new head of the for-next branch is commit:
2cdb958 Merge branch 'xfs-misc-fixes-4.6-4' into for-next
New Commits:
Brian Foster (4):
[801cc4e] xfs: debug mode forced buffered write failure
[b2706a0] xfs: update freeblocks counter after extent deletion
[a9bd24a] xfs: refactor delalloc indlen reservation split into helper
[d34999c] xfs: borrow indirect blocks from freed extent when available
Christoph Hellwig (1):
[355cced] xfs: always set rvalp in xfs_dir2_node_trim_free
Dave Chinner (1):
[2cdb958] Merge branch 'xfs-misc-fixes-4.6-4' into for-next
Eric Sandeen (1):
[cc07eed] xfs: ensure committed is initialized in xfs_trans_roll
Code Diffstat:
fs/xfs/libxfs/xfs_bmap.c | 157 ++++++++++++++++++++++++++++++++------------
fs/xfs/libxfs/xfs_dir2_node.c | 4 +-
fs/xfs/xfs_aops.c | 9 ++-
fs/xfs/xfs_mount.h | 25 +++++++
fs/xfs/xfs_sysfs.c | 78 +++++++++++++++++++---
fs/xfs/xfs_trans.c | 4 +-
6 files changed, 221 insertions(+), 56 deletions(-)
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2016-03-15 20:39 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=20160315203908.GE11812@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
/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