[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8f7a6b33-8fd5-06bf-f6bf-833d29382f88@suse.com>
Date: Wed, 20 Nov 2019 10:03:05 +0200
From: Nikolay Borisov <nborisov@...e.com>
To: ira.weiny@...el.com, Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH] mm: Clean up filemap_write_and_wait()
On 20.11.19 г. 8:23 ч., ira.weiny@...el.com wrote:
> From: Ira Weiny <ira.weiny@...el.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@...el.com>
Reviewed-by: Nikolay Borisov <nborisov@...e.com>
Powered by blists - more mailing lists