linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs <linux-xfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Andreas Gruenbacher <agruenba@redhat.com>,
	Damien Le Moal <Damien.LeMoal@wdc.com>
Subject: [ANNOUNCE] xfs-linux: iomap-for-next updated to 68494b8e248f
Date: Wed, 4 Sep 2019 11:11:13 -0700	[thread overview]
Message-ID: <20190904181113.GK5340@magnolia> (raw)

Hi folks,

The iomap-for-next branch of the xfs-linux repository at:

	git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git

has just been updated.

Patches often get missed, so please check if your outstanding patches
were in this update. If they have not been in this update, please
resubmit them to linux-xfs@vger.kernel.org so they can be picked up in
the next update.  I will send around for review an amended zonefs patch
with the recent api breakage fixed.

The new head of the iomap-for-next branch is commit:

68494b8e248f iomap: move the iomap_dio_rw ->end_io callback into a structure

New Commits:

Andreas Gruenbacher (1):
      [791ee52eb10b] iomap: Fix trivial typo

Christoph Hellwig (9):
      [31c20dede460] list.h: add list_pop and list_pop_entry helpers
      [a12c4b4602f1] iomap: copy the xfs writeback code to iomap.c
      [4b45a4b5c1f5] iomap: add tracing for the address space operations
      [6f0af1def491] iomap: warn on inline maps in iomap_writepage_map
      [84be4599c1a6] xfs: set IOMAP_F_NEW more carefully
      [f61be89fed56] iomap: zero newly allocated mapped blocks
      [3d2d71b4fdff] xfs: initialize iomap->flags in xfs_bmbt_to_iomap
      [1c1daa47a0ae] xfs: refactor the ioend merging code
      [68494b8e248f] iomap: move the iomap_dio_rw ->end_io callback into a structure

Matthew Bobrowski (1):
      [db10bd824bc0] iomap: split size and error for iomap_dio_rw ->end_io

Randy Dunlap (1):
      [32e3cf9f41c7] tracing: fix iomap.h build warnings


Code Diffstat:

 fs/iomap/buffered-io.c       | 575 ++++++++++++++++++++++++++++++++++++++++++-
 fs/iomap/direct-io.c         |  24 +-
 fs/xfs/xfs_aops.c            |  70 +++---
 fs/xfs/xfs_file.c            |  14 +-
 fs/xfs/xfs_iomap.c           |  35 ++-
 fs/xfs/xfs_iomap.h           |   2 +-
 fs/xfs/xfs_pnfs.c            |   2 +-
 include/linux/iomap.h        |  53 +++-
 include/linux/list.h         |  33 +++
 include/trace/events/iomap.h |  87 +++++++
 10 files changed, 824 insertions(+), 71 deletions(-)
 create mode 100644 include/trace/events/iomap.h

                 reply	other threads:[~2019-09-04 18:11 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=20190904181113.GK5340@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=agruenba@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).