From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 04991F2 for ; Sun, 3 Dec 2023 20:55:30 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 13AB5227AA8; Mon, 4 Dec 2023 05:55:27 +0100 (CET) Date: Mon, 4 Dec 2023 05:55:26 +0100 From: Christoph Hellwig To: "Darrick J. Wong" Cc: chandanbabu@kernel.org, hch@lst.de, linux-xfs@vger.kernel.org Subject: Re: [PATCH 1/3] xfs: make rextslog computation consistent with mkfs Message-ID: <20231204045526.GA26073@lst.de> References: <170162990622.3038044.5313475096294285406.stgit@frogsfrogsfrogs> <170162990643.3038044.15276614586917381582.stgit@frogsfrogsfrogs> Precedence: bulk X-Mailing-List: linux-xfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <170162990643.3038044.15276614586917381582.stgit@frogsfrogsfrogs> User-Agent: Mutt/1.5.17 (2007-11-01) > + */ > +uint8_t > +xfs_compute_rextslog( > + xfs_rtbxlen_t rtextents) > +{ > + return rtextents ? xfs_highbit32(rtextents) : 0; It might just be a personal pet peeve, but I find a good old if much more readable for this: if (!rtextents) return 0; return xfs_highbit32(rtextents); Otherwise looks good: Reviewed-by: Christoph Hellwig