[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0e17c0a7-9b40-12a4-3f3f-500b9abb66de@web.de>
Date: Fri, 22 Nov 2019 09:11:00 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Namjae Jeon <namjae.jeon@...sung.com>,
linux-fsdevel@...r.kernel.org
Cc: 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 04/13] exfat: add directory operations
>> …
>>> +++ b/fs/exfat/dir.c
>> …
>>> +static int exfat_readdir(struct inode *inode, struct exfat_dir_entry
>> *dir_entry)
>>> +{
>> …
>>> + if (!ep) {
>>> + ret = -EIO;
>>> + goto free_clu;
>>> + }
>>
>> How do you think about to move a bit of common exception handling code
>> (at similar places)?
> Not sure it is good.
The software development opinions can vary also for this change pattern
according to different design goals.
Is such a transformation just another possibility to reduce duplicate
source code a bit?
Regards,
Markus
Powered by blists - more mailing lists