From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch updated to f2bdfda
Date: Fri, 22 Jul 2016 14:23:36 +1000 [thread overview]
Message-ID: <20160722042336.GQ16044@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1455 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:
f2bdfda Merge branch 'xfs-4.8-misc-fixes-4' into for-next
New Commits:
Arnd Bergmann (1):
[f021bd0] xfs: remove dax code from object file when disabled
Brian Foster (1):
[99579cc] xfs: skip dirty pages in ->releasepage()
Dave Chinner (5):
[160ae76] libxfs: directory node splitting does not have an extra block
[b1c5ebb] xfs: allocate log vector buffers outside CIL context lock
[28b783e] xfs: bufferhead chains are invalid after end_page_writeback
[72ccbbe] xfs: remove EXPERIMENTAL tag from sparse inode feature
[f2bdfda] Merge branch 'xfs-4.8-misc-fixes-4' into for-next
Code Diffstat:
fs/xfs/libxfs/xfs_da_btree.c | 59 ++++++-----
fs/xfs/xfs_aops.c | 29 +++++-
fs/xfs/xfs_buf_item.c | 1 +
fs/xfs/xfs_dquot.c | 1 +
fs/xfs/xfs_dquot_item.c | 2 +
fs/xfs/xfs_extfree_item.c | 2 +
fs/xfs/xfs_file.c | 4 +-
fs/xfs/xfs_inode_item.c | 1 +
fs/xfs/xfs_log_cil.c | 258 ++++++++++++++++++++++++++++++++++------------
fs/xfs/xfs_super.c | 4 -
fs/xfs/xfs_trans.h | 1 +
11 files changed, 259 insertions(+), 103 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 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:[~2016-07-22 4:23 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=20160722042336.GQ16044@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