From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: linux-xfs <linux-xfs@vger.kernel.org>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: [ANNOUNCE] xfs-linux: xfs-4.11-merge updated to 1dbba08
Date: Mon, 30 Jan 2017 16:48:54 -0800 [thread overview]
Message-ID: <20170131004854.GE9134@birch.djwong.org> (raw)
Hi folks,
The xfs-4.11-merge branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has just been updated.
Patches often get missed, so please check if your outstanding
patches were in this update. If they have not been in this update,
please resubmit them to linux-xfs@vger.kernel.org so they can be
picked up in the next update.
** NOTE **
This branch is merely a rollup of the fixes I've collected so far for
4.11. The merge window is probably still a ways away, but I thought I'd
get things started ahead of time. If you've sent a patch and it hasn't
been reviewed, you still have time. If you've sent a patch, had it
reviewed, and it still isn't in either 4.10 or this branch, please
resend it to the list.
** NOTE **
Also cc'ing the ext4 list because of the dax changes within.
The new head of the xfs-4.11-merge branch is commit:
1dbba08 xfs: remove unused full argument from bmap
New Commits:
Brian Foster (3):
[a36b926] xfs: pull up iolock from xfs_free_eofblocks()
[c315509] xfs: sync eofblocks scans under iolock are livelock prone
[e4229d6] xfs: fix eofblocks race with file extending async dio writes
Christoph Hellwig (1):
[8ff6daa] iomap: constify struct iomap_ops
Eric Sandeen (5):
[f88ae46] xfs: glean crc status from mp not flags in xfs_btree_init_block_int
[af7d20f] xfs: make xfs_btree_magic more generic
[b6f41e4] xfs: remove boilerplate around xfs_btree_init_block
[64f61ab] xfs: remove unused struct declarations
[1dbba08] xfs: remove unused full argument from bmap
Code Diffstat:
fs/dax.c | 6 ++---
fs/ext2/ext2.h | 2 +-
fs/ext2/inode.c | 4 +--
fs/ext4/ext4.h | 2 +-
fs/ext4/inode.c | 2 +-
fs/internal.h | 2 +-
fs/iomap.c | 18 ++++++-------
fs/xfs/libxfs/xfs_bmap.c | 19 +++----------
fs/xfs/libxfs/xfs_bmap_btree.c | 10 ++-----
fs/xfs/libxfs/xfs_btree.c | 45 ++++++++++++++++++++++---------
fs/xfs/libxfs/xfs_btree.h | 6 +++--
fs/xfs/libxfs/xfs_log_recover.h | 1 -
fs/xfs/xfs_bmap_util.c | 48 ++++++++++++++-------------------
fs/xfs/xfs_bmap_util.h | 5 ++--
fs/xfs/xfs_file.c | 13 ++++++---
fs/xfs/xfs_fsops.c | 39 +++++++--------------------
fs/xfs/xfs_icache.c | 59 ++++++++++++-----------------------------
fs/xfs/xfs_icache.h | 2 --
fs/xfs/xfs_inode.c | 51 +++++++++++++++++++----------------
fs/xfs/xfs_ioctl.c | 4 +--
fs/xfs/xfs_iomap.c | 4 +--
fs/xfs/xfs_iomap.h | 4 +--
fs/xfs/xfs_log.h | 1 -
fs/xfs/xfs_trace.h | 1 -
fs/xfs/xfs_trans.h | 1 -
include/linux/dax.h | 8 +++---
include/linux/iomap.h | 14 +++++-----
27 files changed, 162 insertions(+), 209 deletions(-)
reply other threads:[~2017-01-31 0:51 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=20170131004854.GE9134@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--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).