From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752556AbcBJPMF (ORCPT ); Wed, 10 Feb 2016 10:12:05 -0500 Received: from canardo.mork.no ([148.122.252.1]:38697 "EHLO canardo.mork.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750997AbcBJPMD convert rfc822-to-8bit (ORCPT ); Wed, 10 Feb 2016 10:12:03 -0500 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= To: Andy Shevchenko Cc: Oliver Neukum , Heikki Krogerus , Felipe Balbi , Mathias Nyman , Greg KH , "linux-kernel\@vger.kernel.org" , USB Subject: Re: [PATCH 2/3] usb: type-c: USB Type-C Connector System Software Interface Organization: m References: <1455037283-106479-1-git-send-email-heikki.krogerus@linux.intel.com> <1455037283-106479-3-git-send-email-heikki.krogerus@linux.intel.com> <1455110486.8878.12.camel@suse.com> Date: Wed, 10 Feb 2016 16:11:42 +0100 In-Reply-To: (Andy Shevchenko's message of "Wed, 10 Feb 2016 16:02:45 +0200") Message-ID: <8760xwbnwx.fsf@nemi.mork.no> User-Agent: Gnus/5.130015 (Ma Gnus v0.15) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andy Shevchenko writes: > On Wed, Feb 10, 2016 at 3:21 PM, Oliver Neukum wrote: >> On Wed, 2016-02-10 at 13:56 +0200, Andy Shevchenko wrote: >>> > +out: >>> >>> CodingStyle suggests to do a better label naming. >> >> Names coming from specs are what they are. There is >> no place for coding style here. > > Yes, and how is it related to C label names? It did appear as if you were commenting on the case labels since you quoted two full switch blocks. That's how I read your comment as well. It's now clear that you somehow mean than "out:" is in conflict with CodingStyle. It is still very unclear how, and it does not seem like you intend to make it any clearer since you did not take the opportunity to explain yourself. FWIW, I read the CodingStyle recommendation as: use descriptive labels instead of "foo1", "foo2" etc, where "foo" is typically "err". I do not see this as conflicting with the use of "err" or "out" when there is a single such label in a function. The meaning of those labels are very clear IMHO. Exactly what is it about "out" that is unclear to you here? Could you propose a better alternative if you seriously mean that this needs to be changed? Bjørn