From: Jens Axboe <axboe@kernel.dk>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: viro@ZenIV.linux.org.uk, hch@lst.de, jack@suse.cz,
akpm@linux-foundation.org, linux-block@vger.kernel.org
Subject: Re: [PATCH 0/10 v14] merge request: No wait AIO
Date: Tue, 20 Jun 2017 07:12:33 -0600 [thread overview]
Message-ID: <340357d1-9c11-7dc0-b223-d5b505f8e04c@kernel.dk> (raw)
In-Reply-To: <20170620120549.23147-1-rgoldwyn@suse.de>
On 06/20/2017 06:05 AM, Goldwyn Rodrigues wrote:
> Jens,
>
> As discussed, here are the patches against the block
> tree for merge since the block layer changes had the most conflicts.
> My tree is at https://github.com/goldwynr/linux/tree/nowait-block
>
> Changes since v13:
> + nowait support for dax files in ext4 and xfs
Added for 4.13, thanks.
--
Jens Axboe
prev parent reply other threads:[~2017-06-20 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 12:05 [PATCH 0/10 v14] merge request: No wait AIO Goldwyn Rodrigues
2017-06-20 12:05 ` [PATCH 01/10] fs: Separate out kiocb flags setup based on RWF_* flags Goldwyn Rodrigues
2017-06-20 12:05 ` [PATCH 02/10] fs: Introduce filemap_range_has_page() Goldwyn Rodrigues
2017-06-20 12:05 ` [PATCH 03/10] fs: Use RWF_* flags for AIO operations Goldwyn Rodrigues
2017-06-20 12:05 ` [PATCH 04/10] fs: Introduce RWF_NOWAIT and FMODE_AIO_NOWAIT Goldwyn Rodrigues
2017-06-20 12:05 ` [PATCH 05/10] fs: return if direct I/O will trigger writeback Goldwyn Rodrigues
2017-06-20 12:05 ` [PATCH 06/10] fs: Introduce IOMAP_NOWAIT Goldwyn Rodrigues
2017-06-20 12:05 ` [PATCH 07/10] block: return on congested block device Goldwyn Rodrigues
2017-06-20 12:05 ` [PATCH 08/10] ext4: nowait aio support Goldwyn Rodrigues
2017-06-20 12:05 ` [PATCH 09/10] xfs: " Goldwyn Rodrigues
2017-06-20 12:05 ` [PATCH 10/10] btrfs: " Goldwyn Rodrigues
2017-06-20 13:12 ` Jens Axboe [this message]
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=340357d1-9c11-7dc0-b223-d5b505f8e04c@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=rgoldwyn@suse.de \
--cc=viro@ZenIV.linux.org.uk \
/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