From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755473AbdKBINF (ORCPT ); Thu, 2 Nov 2017 04:13:05 -0400 Received: from kirsty.vergenet.net ([202.4.237.240]:43665 "EHLO kirsty.vergenet.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755163AbdKBINA (ORCPT ); Thu, 2 Nov 2017 04:13:00 -0400 Date: Thu, 2 Nov 2017 09:12:40 +0100 From: Simon Horman To: SF Markus Elfring Cc: linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Bjorn Helgaas , Laurent Pinchart , LKML , kernel-janitors@vger.kernel.org Subject: Re: PCI: rcar: Use common error handling code in rcar_pcie_enable_msi() Message-ID: <20171102081239.bzaunax3uotejqja@verge.net.au> References: <20171101081831.ssnuqp5b75lbfu5p@verge.net.au> <7047eb7a-cf93-6a56-08db-a5e8bedbfc57@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <7047eb7a-cf93-6a56-08db-a5e8bedbfc57@users.sourceforge.net> Organisation: Horms Solutions BV User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 01, 2017 at 09:57:00AM +0100, SF Markus Elfring wrote: > > This is fine by me > > Thanks for another bit of change acceptance. > > > > except that the change in the name of the goto label seems spurious. > > I am curious if the popularity of a jump label like “err” will decrease > (in the Linux source files) over time. If your current patch bombing is successful then it will, at least in the short term. But my comments relate to the current best practice, not the one you seem to be trying to introduce. > > But if you really want to change it then as it is an error path > > I should suggest it describe that its an error and what unwinding > > is done, f.e. err_remove_domain. > > * Do you get such a kind of information only when the prefix “err_” > is added to this identifier? Yes, err indicates its an error path. > > * Do you prefer to stress the “domain removal” > (or the shown error message) in the label? I prefer to stress the unwind path as that is the most important aspect of the error path. I have no interest in a prelonged debate about the naming of labels. As I pointed out its a spurious aspect of your change. If you wish me to Ack your change then please either drop that change or update it - as I already suggested. Else lets discontinue this sub-thread. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Horman Date: Thu, 02 Nov 2017 08:12:40 +0000 Subject: Re: PCI: rcar: Use common error handling code in rcar_pcie_enable_msi() Message-Id: <20171102081239.bzaunax3uotejqja@verge.net.au> List-Id: References: <20171101081831.ssnuqp5b75lbfu5p@verge.net.au> <7047eb7a-cf93-6a56-08db-a5e8bedbfc57@users.sourceforge.net> In-Reply-To: <7047eb7a-cf93-6a56-08db-a5e8bedbfc57@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit To: SF Markus Elfring Cc: linux-pci@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Bjorn Helgaas , Laurent Pinchart , LKML , kernel-janitors@vger.kernel.org On Wed, Nov 01, 2017 at 09:57:00AM +0100, SF Markus Elfring wrote: > > This is fine by me > > Thanks for another bit of change acceptance. > > > > except that the change in the name of the goto label seems spurious. > > I am curious if the popularity of a jump label like “err” will decrease > (in the Linux source files) over time. If your current patch bombing is successful then it will, at least in the short term. But my comments relate to the current best practice, not the one you seem to be trying to introduce. > > But if you really want to change it then as it is an error path > > I should suggest it describe that its an error and what unwinding > > is done, f.e. err_remove_domain. > > * Do you get such a kind of information only when the prefix “err_” > is added to this identifier? Yes, err indicates its an error path. > > * Do you prefer to stress the “domain removal” > (or the shown error message) in the label? I prefer to stress the unwind path as that is the most important aspect of the error path. I have no interest in a prelonged debate about the naming of labels. As I pointed out its a spurious aspect of your change. If you wish me to Ack your change then please either drop that change or update it - as I already suggested. Else lets discontinue this sub-thread.