From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch rebased to 4faac78
Date: Tue, 9 Feb 2016 17:49:40 +1100 [thread overview]
Message-ID: <20160209064940.GQ27429@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2803 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 is a rebase due to needing to fix the
commits in the xfs-rt-fixes-4.6 branch due to a build failure. It
also includes the struct xfs_icdinode size reduction patchset.
See the commit list below for all the new commits compared to the
previous for-next branch.
-Dave.
The new head of the for-next branch is commit:
4faac78 Merge branch 'xfs-gut-icdinode-4.6' into for-next
New Commits:
Dave Chinner (16):
[f67ca6e] xfs: RT bitmap and summary buffers are not typed
[bf85e09] xfs: RT bitmap and summary buffers need verifiers
[f8d55aa] xfs: introduce inode log format object
[3987848] xfs: remove timestamps from incore inode
[93f958f] xfs: cull unnecessary icdinode fields
[faeb4e4] xfs: move v1 inode conversion to xfs_inode_from_disk
[5099747] xfs: reinitialise recycled VFS inode correctly
[54d7b5c] xfs: use vfs inode nlink field everywhere
[9e9a267] xfs: move inode generation count to VFS inode
[83e06f2] xfs: move di_changecount to VFS inode
[c19b3b05] xfs: mode di_mode to vfs inode
[fc0f49c] Merge branch 'xfs-rt-fixes-4.6' into for-next
[4f22770] Merge branch 'xfs-get-next-dquot-4.6' into for-next
[0294f79] Merge branch 'xfs-dio-fix-4.6' into for-next
[18c5e03] Merge branch 'xfs-misc-fixes-4.6' into for-next
[4faac78] Merge branch 'xfs-gut-icdinode-4.6' into for-next
Code Diffstat:
fs/xfs/libxfs/xfs_bmap.c | 6 +-
fs/xfs/libxfs/xfs_dir2.c | 12 +--
fs/xfs/libxfs/xfs_inode_buf.c | 170 ++++++++++++++++++++++++++--------------
fs/xfs/libxfs/xfs_inode_buf.h | 38 ++++++++-
fs/xfs/libxfs/xfs_inode_fork.c | 2 +-
fs/xfs/libxfs/xfs_log_format.h | 17 ++--
fs/xfs/libxfs/xfs_rtbitmap.c | 2 +-
fs/xfs/xfs_bmap_util.c | 4 +-
fs/xfs/xfs_dir2_readdir.c | 2 +-
fs/xfs/xfs_export.c | 2 +-
fs/xfs/xfs_file.c | 6 +-
fs/xfs/xfs_filestream.c | 4 +-
fs/xfs/xfs_icache.c | 43 +++++++++--
fs/xfs/xfs_inode.c | 172 +++++++++++++++++------------------------
fs/xfs/xfs_inode.h | 8 +-
fs/xfs/xfs_inode_item.c | 82 ++++++++++++++++++--
fs/xfs/xfs_ioctl.c | 16 ++--
fs/xfs/xfs_iops.c | 53 +++----------
fs/xfs/xfs_itable.c | 22 +++---
fs/xfs/xfs_log_recover.c | 60 +++++++-------
fs/xfs/xfs_mount.c | 2 +-
fs/xfs/xfs_rtalloc.c | 2 +-
fs/xfs/xfs_trans_inode.c | 14 +---
23 files changed, 431 insertions(+), 308 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:[~2016-02-09 6: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=20160209064940.GQ27429@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