[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e427d4ad-aaa0-1d96-3aab-01be7703dd77@web.de>
Date: Tue, 19 Nov 2019 15:19:01 +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>,
Sungjong Seo <sj1557.seo@...sung.com>,
Valdis Klētnieks <valdis.kletnieks@...edu>,
linkinjeon@...il.com
Subject: Re: [PATCH v3 06/13] exfat: add exfat entry operations
…
> +++ b/fs/exfat/fatent.c
…
> +int exfat_zeroed_cluster(struct inode *dir, unsigned int clu)
> +{
…
> +error:
> + exfat_msg(sb, KERN_ERR, "failed zeroed sect %llu\n",
> + (unsigned long long)blknr);
…
Can the label “report_failure” be more helpful?
…
> +int exfat_alloc_cluster(struct inode *inode, unsigned int num_alloc,
> + struct exfat_chain *p_chain)
> +{
…
> +error:
> + if (num_clusters)
> + exfat_free_cluster(inode, p_chain);
Can a label like “check_num_clusters” be nicer?
Regards,
Markus
Powered by blists - more mailing lists