[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAO3upoYjXOKN2O+ZQuS_LfiWd3PnzAZ5UB4xHivMSFgqaNBtcQ@mail.gmail.com>
Date: Mon, 16 Jul 2018 14:15:51 -0700
From: Todd Poynor <toddpoynor@...il.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Rob Springer <rspringer@...gle.com>,
John Joseph <jnjoseph@...gle.com>,
Ben Chan <benchan@...omium.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
devel@...verdev.osuosl.org, Zhongze Hu <frankhu@...omium.org>,
lkml <linux-kernel@...r.kernel.org>,
Simon Que <sque@...omium.org>,
Guenter Roeck <groeck@...omium.org>,
Todd Poynor <toddpoynor@...gle.com>,
Dmitry Torokhov <dtor@...omium.org>
Subject: Re: [PATCH 04/18] staging: gasket: device registration error and
unregister fixups
>> fail1:
>> class_destroy(internal->class);
>>
>> +fail0:
>
> GW-BASIC sytle label names are an anti-pattern. It's better to name the
> labels after what they do, just like function names describes what the
> function does. Here it would be "goto clear_desc;" or something. It
> doesn't have to be perfect but so long as you *try* to name it something
> useful that's better than not trying.
>
>> + mutex_lock(&g_mutex);
>> g_descs[desc_idx].driver_desc = NULL;
>> + mutex_unlock(&g_mutex);
>> return ret;
>> }
>
> regards,
> dan carpenter
Thanks, I'll fix up the newly-added one in a respin of this patch and
fix up existing labels in a future patch.
--
Todd
Powered by blists - more mailing lists