From: Jens Axboe <axboe@kernel.dk>
To: Jan Kara <jack@suse.cz>, Gabriel Krisman Bertazi <krisman@collabora.com>
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
kernel@collabora.com
Subject: Re: [RESEND^2 PATCH v3 0/3] Clean up and fix error handling in DIO
Date: Thu, 8 Oct 2020 10:16:07 -0600 [thread overview]
Message-ID: <b8e122ef-d36b-c107-dae6-29fce6a69e26@kernel.dk> (raw)
In-Reply-To: <20201008093213.GB3486@quack2.suse.cz>
On 10/8/20 3:32 AM, Jan Kara wrote:
> On Thu 08-10-20 02:26:17, Gabriel Krisman Bertazi wrote:
>> Hi,
>>
>> Given the proximity of the merge window and since I haven't seen it pop
>> up in any of the trees, and considering it is reviewed and fixes a bug
>> for us, I'm trying another resend for this so it can get picked up in
>> time for 5.10.
>>
>> Jan, thanks again for the review and sorry for the noise but is there
>> any one else that should be looking at this?
>
> If you can't catch attention of Al Viro, then Jens Axboe is sometimes
> merging direct IO fixes as well through his tree. Added to CC. If that
> doesn't work out, I can also take the changes through my tree and send them
> to Linus in a separate pull request...
For this case, probably best if you take it, Jan. I looked over the
patches and they look good to me, feel free to add:
Reviewed-by: Jens Axboe <axboe@kernel.dk>
--
Jens Axboe
next prev parent reply other threads:[~2020-10-08 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 6:26 [RESEND^2 PATCH v3 0/3] Clean up and fix error handling in DIO Gabriel Krisman Bertazi
2020-10-08 6:26 ` [RESEND^2 PATCH 1/3] direct-io: clean up error paths of do_blockdev_direct_IO Gabriel Krisman Bertazi
2020-10-08 6:26 ` [RESEND^2 PATCH 2/3] direct-io: don't force writeback for reads beyond EOF Gabriel Krisman Bertazi
2020-10-08 6:26 ` [RESEND^2 PATCH 3/3] direct-io: defer alignment check until after the EOF check Gabriel Krisman Bertazi
2020-10-08 9:32 ` [RESEND^2 PATCH v3 0/3] Clean up and fix error handling in DIO Jan Kara
2020-10-08 16:16 ` Jens Axboe [this message]
2020-10-08 16:27 ` 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=b8e122ef-d36b-c107-dae6-29fce6a69e26@kernel.dk \
--to=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).