From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julia Lawall Date: Tue, 02 Dec 2014 07:37:32 +0000 Subject: Re: [PATCH v2] fs-fat: Less function calls in fat_fill_super() after error detection Message-Id: List-Id: References: <5467B12C.4010602@users.sourceforge.net> <54796B5E.5040707@users.sourceforge.net> <87sih22sn8.fsf@devron.myhome.or.jp> <87lhmu2jl8.fsf@devron.myhome.or.jp> <20141201065221.GA4994@mwanda> <547C89A4.40002@users.sourceforge.net> <20141201191723.GG4994@mwanda> <547CDC1E.7020404@users.sourceforge.net> <20141202073440.GH4994@mwanda> In-Reply-To: <20141202073440.GH4994@mwanda> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: cocci@systeme.lip6.fr On Tue, 2 Dec 2014, Dan Carpenter wrote: > On Mon, Dec 01, 2014 at 10:22:38PM +0100, SF Markus Elfring wrote: > > >> Which names would be better acceptable for you? > > > > > > You named it after the goto location but the label name should be based > > > on the label location to say what the goto does. > > > > I find it easier occasionally to name a label similarly to the jump target. > > That is a useless thing to do. > > > It seems that there are a few variations used for the affected identifiers. > > There is a lot of crap code in the kernel, yes. Does the label naming strategy appear in the conding style documentation anywhere? There are so many variants that just from looking at the code, it is hard to guess what is the best strategy. For example, out1, out2, etc are pretty uninformative, but they are concise and easy to spell correctly. julia