All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com, linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfs: master branch updated to v4.8-rc2, for-next branch updated to d25ed4d
Date: Wed, 17 Aug 2016 09:36:59 +1000	[thread overview]
Message-ID: <20160816233659.GE19025@dastard> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2323 bytes --]

Hi folks,

I've just updated the master branch of hte XFS kernel repository to
v4.8-rc2. If you have outstanding patches, can you check they apply
to this updated branch, and if not rebase your patches and resend
them?

I've also updated with the for-next branch with the fixes I intend
to send to Linus at the end of the week. This does not include
Christoph's delayed allocation rework - that still needs more testing
before merging. Full details of the commits merged are below.

-Dave.

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:

d25ed4d Merge branch 'iomap-fixes-4.8-rc3' into for-next

New Commits:

Brian Foster (1):
      [4dd3fd7] xfs: don't assert fail on non-async buffers on ioacct decrement

Christoph Hellwig (6):
      [0af32fb] xfs: fix bogus space reservation in xfs_iomap_write_allocate
      [97dd8c9] iomap: remove superflous mark_page_accessed from iomap_write_actor
      [274c887] iomap: remove superflous pagefault_disable from iomap_write_actor
      [f20ac7a] iomap: mark ->iomap_end as optional
      [b95a212] xfs: simplify xfs_file_iomap_begin
      [1d4795e] xfs: (re-)implement FIEMAP_FLAG_XATTR

Darrick J. Wong (1):
      [f32866fd] xfs: store rmapbt block count in the AGF

Dave Chinner (4):
      [8b2180b] xfs: don't invalidate whole file on DAX read/write
      [8896b8f] iomap: fiemap should honor the FIEMAP_FLAG_SYNC flag
      [ac2dc05] iomap: prepare iomap_fiemap for attribute mappings
      [d25ed4d] Merge branch 'iomap-fixes-4.8-rc3' into for-next


Code Diffstat:

 fs/iomap.c                     | 21 ++++++++------
 fs/xfs/libxfs/xfs_alloc.c      |  1 +
 fs/xfs/libxfs/xfs_format.h     | 11 ++++++--
 fs/xfs/libxfs/xfs_rmap_btree.c |  6 ++++
 fs/xfs/xfs_buf.c               |  1 -
 fs/xfs/xfs_file.c              | 13 ++++++++-
 fs/xfs/xfs_fsops.c             |  1 +
 fs/xfs/xfs_iomap.c             | 69 ++++++++++++++++++++++++++++++++++++---------
 fs/xfs/xfs_iomap.h             |  1 +
 fs/xfs/xfs_iops.c              |  9 +++++-
 fs/xfs/xfs_trace.h             |  1 -
 11 files changed, 106 insertions(+), 28 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

             reply	other threads:[~2016-08-16 23:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 23:36 Dave Chinner [this message]
2016-08-17  0:33 ` [ANNOUNCE] xfs: master branch updated to v4.8-rc2, for-next branch updated to d25ed4d Darrick J. Wong
2016-08-17  1:10   ` Dave Chinner
2016-08-17  1:49     ` 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=20160816233659.GE19025@dastard \
    --to=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --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.