[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191122063303.GA16886@lst.de>
Date: Fri, 22 Nov 2019 07:33:03 +0100
From: Christoph Hellwig <hch@....de>
To: Markus Elfring <Markus.Elfring@....de>
Cc: Namjae Jeon <namjae.jeon@...sung.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org, Christoph Hellwig <hch@....de>,
Daniel Wagner <dwagner@...e.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Nikolay Borisov <nborisov@...e.com>,
Sungjong Seo <sj1557.seo@...sung.com>,
Valdis Klētnieks <valdis.kletnieks@...edu>,
linkinjeon@...il.com
Subject: Re: [PATCH v4 03/13] exfat: add inode operations
On Thu, Nov 21, 2019 at 11:40:28AM +0100, Markus Elfring wrote:
> > + err = exfat_map_cluster(inode, clu_offset, &cluster,
> > + *create & BMAP_ADD_CLUSTER);
>
> I find an other indentation more appropriate.
> Please align the last parameter below (or besides) the opening parenthesis.
It is great that you find that, but I think we can leave this to
the code author. We have plenty of example for opening brace aligned,
one or two tabs alignments in the code, and it is up to the author /
maintainer to chose one. No need to to nitpick their choices inside the
boundaries of the normal coding space.
> > + if (err) {
> > + if (err != -ENOSPC)
> > + return -EIO;
> > + return err;
> > + }
>
> Can such source code become more succinct?
>
> + if (err)
> + return err != -ENOSPC ? -EIO : err;
If it sufficient but a lot harder to follow.
Powered by blists - more mailing lists