From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: for-next branch updated to b77428b12b55
Date: Mon, 24 Oct 2016 21:50:35 +1100 [thread overview]
Message-ID: <20161024105035.GZ14023@dastard> (raw)
[-- Attachment #1: Type: text/plain, Size: 964 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:
b77428b12b55 xfs: defer should abort intent items if the trans roll fails
New Commits:
Brian Foster (2):
[7b7381f04356] xfs: fix up inode cowblocks tracking tracepoints
[c17a8ef43d6b] xfs: clear cowblocks tag when cow fork is emptied
Darrick J. Wong (1):
[b77428b12b55] xfs: defer should abort intent items if the trans roll fails
Jan Kara (1):
[c663e29f8885] fs: Do to trim high file position bits in iomap_page_mkwrite_actor
Code Diffstat:
fs/iomap.c | 3 +--
fs/xfs/libxfs/xfs_defer.c | 17 +++++------------
fs/xfs/xfs_icache.c | 8 ++++----
fs/xfs/xfs_reflink.c | 6 +++++-
4 files changed, 15 insertions(+), 19 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2016-10-24 10:51 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=20161024105035.GZ14023@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
/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.