From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch updated to cddc116
Date: Fri, 29 May 2015 07:53:09 +1000 [thread overview]
Message-ID: <20150528215309.GA15721@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1386 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:
cddc116 xfs: xfs_iozero can return positive errno
New Commits:
Dave Chinner (5):
[80188b0] percpu_counter: batch size aware __percpu_counter_compare()
[8c1903d] xfs: inode and free block counters need to use __percpu_counter_compare
[6dea405] xfs: extent size hints can round up extents past MAXEXTLEN
[6dfe5a0] xfs: xfs_attr_inactive leaves inconsistent attr fork state behind
[cddc116] xfs: xfs_iozero can return positive errno
George Wang (1):
[74f9ce1] xfs: use percpu_counter_read_positive for mp->m_icount
Code Diffstat:
fs/xfs/libxfs/xfs_attr_leaf.c | 8 ++--
fs/xfs/libxfs/xfs_attr_leaf.h | 2 +-
fs/xfs/libxfs/xfs_bmap.c | 31 ++++++++++------
fs/xfs/libxfs/xfs_ialloc.c | 9 +++--
fs/xfs/xfs_attr_inactive.c | 83 +++++++++++++++++++++++++-----------------
fs/xfs/xfs_file.c | 2 +-
fs/xfs/xfs_inode.c | 12 ++----
fs/xfs/xfs_mount.c | 34 ++++++++++-------
include/linux/percpu_counter.h | 13 ++++++-
lib/percpu_counter.c | 6 +--
10 files changed, 119 insertions(+), 81 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
next reply other threads:[~2015-05-28 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 21:53 Dave Chinner [this message]
2015-05-28 22:21 ` [ANNOUNCE] xfs: for-next branch updated to cddc116 Dave Chinner
2015-05-29 12:05 ` Brian Foster
2015-05-29 22:31 ` Dave Chinner
2015-05-30 12:06 ` Brian Foster
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=20150528215309.GA15721@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