From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 55243CA9EB9 for ; Sat, 26 Oct 2019 05:47:49 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 31A7C214DA for ; Sat, 26 Oct 2019 05:47:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725966AbfJZFrs (ORCPT ); Sat, 26 Oct 2019 01:47:48 -0400 Received: from verein.lst.de ([213.95.11.211]:54272 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725843AbfJZFrs (ORCPT ); Sat, 26 Oct 2019 01:47:48 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id CC7CF68BFE; Sat, 26 Oct 2019 07:47:46 +0200 (CEST) Date: Sat, 26 Oct 2019 07:47:46 +0200 From: Christoph Hellwig To: Eric Sandeen Cc: Christoph Hellwig , linux-xfs@vger.kernel.org, Ian Kent Subject: Re: [PATCH 5/7] xfs: remove the iosizelog variable in xfs_parseargs Message-ID: <20191026054746.GB14648@lst.de> References: <20191025174026.31878-1-hch@lst.de> <20191025174026.31878-6-hch@lst.de> <31757020-becb-1a54-645b-8bce2c5edf44@sandeen.net> <9817805f-27f0-93bc-2a54-ad0e82c0493b@sandeen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9817805f-27f0-93bc-2a54-ad0e82c0493b@sandeen.net> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-xfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org On Fri, Oct 25, 2019 at 02:03:06PM -0500, Eric Sandeen wrote: > sorry make that "-o allocsize=0" > > Which I guess /is/ documented as being invalid, we just never rejected it > before. > > Still a change in behavior and worth being explicit about I think. I'll updated the changelog to mention that.