From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: for-next branch rebased to 155cd433b516
Date: Mon, 3 Oct 2016 11:06:17 +1100 [thread overview]
Message-ID: <20161003000617.GL27872@dastard> (raw)
[-- Attachment #1: Type: text/plain, Size: 1417 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. This was a rebase as I added fixes to the end
of stable topic branches and remerged them to rebuild the tree
cleanly. The tree, as it sits, is what I plan to send to Linus later
in the week, so if there's anything you notice wrong, please let me
know quickly...
The new head of the for-next branch is commit:
155cd433b516 Merge branch 'xfs-4.9-log-recovery-fixes' into for-next
New Commits:
Christoph Hellwig (3):
[d5bfccdf38d0] ext2: fix possible integer truncation in ext2_iomap_begin
[a447d7cd15c7] xfs: update atime before I/O in xfs_file_dio_aio_read
[0d5b0cf246a3] fs: update atime before I/O in generic_file_read_iter
Dave Chinner (5):
[b036b97050a9] Merge branch 'iomap-4.9-misc-fixes-1' into for-next
[79ad57612495] Merge branch 'xfs-4.9-reflink-prep' into for-next
[a89b3f97bb7c] Merge branch 'xfs-4.9-delalloc-rework' into for-next
[a1f45e668e14] Merge branch 'iomap-4.9-dax' into for-next
[155cd433b516] Merge branch 'xfs-4.9-log-recovery-fixes' into for-next
Code Diffstat:
fs/ext2/inode.c | 2 +-
fs/xfs/xfs_file.c | 3 ++-
mm/filemap.c | 14 +++++++-------
3 files changed, 10 insertions(+), 9 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2016-10-03 0:06 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=20161003000617.GL27872@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.