From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
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: Re: [ANNOUNCE] xfs-linux: iomap-5.5-merge updated to c9acd3aee077
Date: Tue, 15 Oct 2019 09:55:54 -0700 [thread overview]
Message-ID: <20191015165554.GA10728@infradead.org> (raw)
In-Reply-To: <20191015164901.GF13108@magnolia>
On Tue, Oct 15, 2019 at 09:49:01AM -0700, Darrick J. Wong wrote:
>
> Jan Kara (2):
> [13ef954445df] iomap: Allow forcing of waiting for running DIO in iomap_dio_rw()
> [c9acd3aee077] xfs: Use iomap_dio_rw_wait()
The second commit seems to be mis-titled as there is no function
called iomap_dio_rw_wait in that tree.
next prev parent reply other threads:[~2019-10-15 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 16:49 [ANNOUNCE] xfs-linux: iomap-5.5-merge updated to c9acd3aee077 Darrick J. Wong
2019-10-15 16:55 ` Christoph Hellwig [this message]
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=20191015165554.GA10728@infradead.org \
--to=hch@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=agruenba@redhat.com \
--cc=darrick.wong@oracle.com \
--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).