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>, Jan Kara <jack@suse.cz>,
	mbobrowski@mbobrowski.org
Subject: [ANNOUNCE] xfs-linux: iomap-5.5-merge updated to c9acd3aee077
Date: Tue, 15 Oct 2019 09:49:01 -0700	[thread overview]
Message-ID: <20191015164901.GF13108@magnolia> (raw)

Hi folks,

The iomap-5.5-merge 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.  The intent is to establish this as a stable branch for
everyone else's 5.5 development activities by the end of the week.

Note that this is an interim update, since I intend to review
Christoph's v5 iomap writeback series when I'm done sending these
announcements.

The new head of the iomap-5.5-merge branch is commit:

c9acd3aee077 xfs: Use iomap_dio_rw_wait()

New Commits:

Jan Kara (2):
      [13ef954445df] iomap: Allow forcing of waiting for running DIO in iomap_dio_rw()
      [c9acd3aee077] xfs: Use iomap_dio_rw_wait()


Code Diffstat:

 fs/gfs2/file.c        |  6 ++++--
 fs/iomap/direct-io.c  |  7 +++++--
 fs/xfs/xfs_file.c     | 13 +++++--------
 include/linux/iomap.h |  3 ++-
 4 files changed, 16 insertions(+), 13 deletions(-)

             reply	other threads:[~2019-10-15 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15 16:49 Darrick J. Wong [this message]
2019-10-15 16:55 ` [ANNOUNCE] xfs-linux: iomap-5.5-merge updated to c9acd3aee077 Christoph Hellwig
2019-10-15 17:36   ` Darrick J. Wong
2019-10-16  9:35     ` Jan Kara

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=20191015164901.GF13108@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=agruenba@redhat.com \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mbobrowski@mbobrowski.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).