From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:55871 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936176AbdIZGdP (ORCPT ); Tue, 26 Sep 2017 02:33:15 -0400 Date: Tue, 26 Sep 2017 08:33:14 +0200 From: Christoph Hellwig Subject: Re: [PATCH 5/7] xfs: introduce xfs_is_dax_state_changing Message-ID: <20170926063314.GB6870@lst.de> References: <20170925231404.32723-1-ross.zwisler@linux.intel.com> <20170925231404.32723-6-ross.zwisler@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170925231404.32723-6-ross.zwisler@linux.intel.com> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Ross Zwisler Cc: Andrew Morton , linux-kernel@vger.kernel.org, "Darrick J. Wong" , "J. Bruce Fields" , Christoph Hellwig , Dan Williams , Dave Chinner , Jan Kara , Jeff Layton , linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-nvdimm@lists.01.org, linux-xfs@vger.kernel.org > +static bool > +xfs_is_dax_state_changing( > + unsigned int xflags, > + struct xfs_inode *ip) And I have no fricking idea what 'is_dax_state_changing' is supposed to mean for the caller. This needs a better name and/or a comment explaining the function.