Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 20 Nov 2019 05:36:19 -0800
From:   Matthew Wilcox <willy@infradead.org>
To:     ira.weiny@intel.com
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
        linux-mm@kvack.org
Subject: Re: [PATCH] mm: Clean up filemap_write_and_wait()
Message-ID: <20191120133619.GR20752@bombadil.infradead.org>
References: <20191120062334.24687-1-ira.weiny@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20191120062334.24687-1-ira.weiny@intel.com>
User-Agent: Mutt/1.12.1 (2019-06-15)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Nov 19, 2019 at 10:23:34PM -0800, ira.weiny@intel.com wrote:
> 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: Matthew Wilcox (Oracle) <willy@infradead.org>