From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs; for-next branch updated to 31bb236
Date: Wed, 2 Mar 2016 10:15:11 +1100 [thread overview]
Message-ID: <20160301231511.GM30721@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1368 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:
31bb236 Merge branch 'xfs-misc-fixes-4.6-2' into for-next
New Commits:
Christoph Hellwig (1):
[a7e5d03] xfs: remove xfs_trans_get_block_res
Colin Ian King (1):
[5d518bd] xfs: fix format specifier , should be %llx and not %llu
Dave Chinner (1):
[31bb236] Merge branch 'xfs-misc-fixes-4.6-2' into for-next
Eric Sandeen (3):
[2e74af0] xfs: convert mount option parsing to tokens
[a08ee40] xfs: sanitize remount options
[12c3f05] xfs: fix up inode32/64 (re)mount handling
Mateusz Guzik (1):
[2e83b79] xfs: fix two memory leaks in xfs_attr_list.c error paths
Code Diffstat:
fs/xfs/libxfs/xfs_bmap.c | 6 +-
fs/xfs/libxfs/xfs_bmap_btree.c | 4 +-
fs/xfs/xfs_attr_list.c | 19 +-
fs/xfs/xfs_discard.c | 2 +-
fs/xfs/xfs_mount.c | 20 +-
fs/xfs/xfs_mount.h | 5 +-
fs/xfs/xfs_super.c | 525 +++++++++++++++++++++++--------------------
fs/xfs/xfs_super.h | 4 +-
fs/xfs/xfs_trans.h | 1 -
9 files changed, 304 insertions(+), 282 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
next reply other threads:[~2016-03-02 0:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 23:15 Dave Chinner [this message]
2016-03-02 9:45 ` [ANNOUNCE] xfs; for-next branch updated to 31bb236 Christoph Hellwig
2016-03-02 21:09 ` Dave Chinner
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=20160301231511.GM30721@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