From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch updated to 542c311
Date: Thu, 16 Apr 2015 22:55:33 +1000 [thread overview]
Message-ID: <20150416125533.GD21261@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1138 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.
The new head of the for-next branch is commit:
542c311 Merge branch 'xfs-dio-extend-fix' into for-next
New Commits:
Dave Chinner (9):
[a719370] xfs: factor DIO write mapping from get_blocks
[1fdca9c] xfs: move DIO mapping size calculation
[d5cc2e3] xfs: DIO needs an ioend for writes
[6dfa1b6] xfs: handle DIO overwrite EOF update completion correctly
[a06c277] xfs: DIO writes within EOF don't need an ioend
[b9d5984] xfs: DIO write completion size updates race
[40c63fb] xfs: direct IO EOF zeroing needs to drain AIO
[0cefb29] xfs: using generic_file_direct_write() is unnecessary
[542c311] Merge branch 'xfs-dio-extend-fix' into for-next
Code Diffstat:
fs/xfs/xfs_aops.c | 270 +++++++++++++++++++++++++++++++++++++----------------
fs/xfs/xfs_file.c | 46 ++++++++-
fs/xfs/xfs_trace.h | 5 +
3 files changed, 239 insertions(+), 82 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2015-04-16 12:55 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=20150416125533.GD21261@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 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.