From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch updated to ee3804d
Date: Wed, 20 Jan 2016 08:42:31 +1100 [thread overview]
Message-ID: <20160119214231.GS6033@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1576 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 contains a couple of regression fixes
for the recent 4.5 merge, and the XFS_IOC_FS[SG]SETXATTR API vfs
promotion that I forgot to merge into the original pull request.
If nothing comes up, I'll ask Linus to pull these in a couple of
days time.
-Dave.
The new head of the for-next branch is commit:
ee3804d Merge branch 'xfs-misc-fixes-for-4.5-3' into for-next
New Commits:
Dave Chinner (7):
[334e580] fs: XFS_IOC_FS[SG]SETXATTR to FS_IOC_FS[SG]ETXATTR promotion
[e7b8948] xfs: use FS_XFLAG definitions directly
[58f88ca] xfs: introduce per-inode DAX enablement
[4c931f7] Merge branch 'xfs-setxattr-promotion' into for-next
[3e85286] Revert "xfs: clear PF_NOFREEZE for xfsaild kthread"
[85bec54] xfs: log mount failures don't wait for buffers to be released
[ee3804d] Merge branch 'xfs-misc-fixes-for-4.5-3' into for-next
Code Diffstat:
fs/xfs/libxfs/xfs_format.h | 11 +++++-
fs/xfs/libxfs/xfs_fs.h | 38 +------------------
fs/xfs/xfs_buf.c | 10 +++++
fs/xfs/xfs_inode.c | 60 ++++++++++++++++++------------
fs/xfs/xfs_ioctl.c | 92 +++++++++++++++++++++++++++-------------------
fs/xfs/xfs_iops.c | 4 +-
fs/xfs/xfs_trans_ail.c | 1 -
include/uapi/linux/fs.h | 33 +++++++++++++++++
8 files changed, 147 insertions(+), 102 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-01-19 21:42 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=20160119214231.GS6033@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.