From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: for-next branch updated to b7b26110edf8
Date: Mon, 28 Nov 2016 15:49:45 +1100 [thread overview]
Message-ID: <20161128044944.GZ28177@dastard> (raw)
[-- Attachment #1: Type: text/plain, Size: 2915 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.
-Dave.
The new head of the for-next branch is commit:
b7b26110edf8 Merge branch 'xfs-4.10-misc-fixes-2' into for-next
New Commits:
Bhumika Goyal (2):
[bb6e0ebed7f7] fs: xfs: xfs_icreate_item: constify xfs_item_ops structure
[cf7841c12d85] fs: xfs: libxfs: constify xfs_nameops structures
Brian Foster (3):
[974ae922efd9] xfs: track preallocation separately in xfs_bmapi_reserve_delalloc()
[0260d8ff5f76] xfs: clean up cow fork reservation and tag inodes correctly
[f782088c9e5d] xfs: pass post-eof speculative prealloc blocks to bmapi
Christoph Hellwig (14):
[93533c7855c3] xfs: new inode extent list lookup helpers
[86685f7ba5c0] xfs: cleanup xfs_bmap_last_before
[334f3423d6a6] xfs: use new extent lookup helpers in xfs_bmapi_read
[2d58f6ef79db] xfs: use new extent lookup helpers in xfs_bmapi_write
[7efc794561f6] xfs: use new extent lookup helpers in __xfs_bunmapi
[65c5f419788d] xfs: remove prev argument to xfs_bmapi_reserve_delalloc
[656152e552e5] xfs: use new extent lookup helpers xfs_file_iomap_begin_delay
[2755fc443850] xfs: use new extent lookup helpers in __xfs_reflink_reserve_cow
[092d5d9d5812] xfs: cleanup xfs_reflink_find_cow_mapping
[86f12ab05ffc] xfs: use new extent lookup helpers in xfs_reflink_trim_irec_to_next_cow
[df5ab1b5a841] xfs: use new extent lookup helpers in xfs_reflink_cancel_cow_blocks
[4ab8671c1962] xfs: use new extent lookup helpers in xfs_reflink_end_cow
[6edc977f775e] xfs: remove xfs_bmap_search_extents
[0e8d630ba039] xfs: remove NULLEXTNUM
Darrick J. Wong (2):
[fd26a88093ba] xfs: factor rmap btree size into the indlen calculations
[fba3e594ef0a] xfs: always succeed when deduping zero bytes
Dave Chinner (2):
[ed24bee6f26b] Merge branch 'xfs-4.10-extent-lookup' into for-next
[b7b26110edf8] Merge branch 'xfs-4.10-misc-fixes-2' into for-next
Eric Sandeen (1):
[1247ec4c5f6e] xfs: add XBF_XBF_NO_IOACCT to buf trace output
Code Diffstat:
fs/xfs/libxfs/xfs_bmap.c | 274 +++++++++++++++--------------------------
fs/xfs/libxfs/xfs_bmap.h | 9 +-
fs/xfs/libxfs/xfs_dir2.c | 2 +-
fs/xfs/libxfs/xfs_inode_fork.c | 46 +++++++
fs/xfs/libxfs/xfs_inode_fork.h | 6 +
fs/xfs/libxfs/xfs_types.h | 1 -
fs/xfs/xfs_aops.c | 16 +--
fs/xfs/xfs_buf.h | 1 +
fs/xfs/xfs_icreate_item.c | 2 +-
fs/xfs/xfs_iomap.c | 54 ++++----
fs/xfs/xfs_reflink.c | 143 ++++++++-------------
fs/xfs/xfs_reflink.h | 4 +-
12 files changed, 239 insertions(+), 319 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2016-11-28 4:49 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=20161128044944.GZ28177@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;
as well as URLs for NNTP newsgroup(s).