From: Chao Yu <yuchao0@huawei.com>
To: Lihong Kou <koulihong@huawei.com>, <jaegeuk@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
fangwei1@huawei.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: remove duplicate code in f2fs_file_write_iter
Date: Mon, 5 Aug 2019 15:29:39 +0800 [thread overview]
Message-ID: <0bcef312-96b0-4630-6001-e3e2fe102e71@huawei.com> (raw)
In-Reply-To: <1564990044-107117-1-git-send-email-koulihong@huawei.com>
On 2019/8/5 15:27, Lihong Kou wrote:
> We will do the same check in generic_write_checks.
> if (iocb->ki_flags & IOCB_NOWAIT) && !(iocb->ki_flags & IOCB_DIRECT)
> return -EINVAL;
> just remove the same check in f2fs_file_write_iter.
>
> Signed-off-by: Lihong Kou <koulihong@huawei.com>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2019-08-05 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 7:27 [f2fs-dev] [PATCH] f2fs: remove duplicate code in f2fs_file_write_iter Lihong Kou
2019-08-05 7:29 ` Chao Yu [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=0bcef312-96b0-4630-6001-e3e2fe102e71@huawei.com \
--to=yuchao0@huawei.com \
--cc=fangwei1@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=koulihong@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).