From: Nikolay Borisov <nborisov@suse.com>
To: ira.weiny@intel.com, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm: Clean up filemap_write_and_wait()
Date: Wed, 20 Nov 2019 10:03:05 +0200 [thread overview]
Message-ID: <8f7a6b33-8fd5-06bf-f6bf-833d29382f88@suse.com> (raw)
In-Reply-To: <20191120062334.24687-1-ira.weiny@intel.com>
On 20.11.19 г. 8:23 ч., ira.weiny@intel.com wrote:
> From: Ira Weiny <ira.weiny@intel.com>
>
> At some point filemap_write_and_wait() and
> filemap_write_and_wait_range() got the exact same implementation with
> the exception of the range being specified in *_range()
>
> Similar to other functions in fs.h which call
> *_range(..., 0, LLONG_MAX), change filemap_write_and_wait() to be a
> static inline which calls filemap_write_and_wait_range()
>
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
next prev parent reply other threads:[~2019-11-20 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 6:23 ira.weiny
2019-11-20 8:03 ` Nikolay Borisov [this message]
2019-11-20 13:36 ` Matthew Wilcox
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=8f7a6b33-8fd5-06bf-f6bf-833d29382f88@suse.com \
--to=nborisov@suse.com \
--cc=akpm@linux-foundation.org \
--cc=ira.weiny@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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