From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Carpenter Date: Sat, 17 May 2014 22:42:55 +0000 Subject: Re: [PATCH 2/4] cpupower: Remove redundant error check Message-Id: <20140517224255.GJ15585@mwanda> List-Id: References: <1400350980-30455-2-git-send-email-peter.senna@gmail.com> <20140517202255.GF15585@mwanda> <20140517215615.GI16255@mwanda> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Peter Senna Tschudin Cc: Dominik Brodowski , Thomas Renninger , "linux-kernel@vger.kernel.org" , "Rafael J. Wysocki" , Alan Cox , kernel-janitors@vger.kernel.org On Sun, May 18, 2014 at 12:31:29AM +0200, Peter Senna Tschudin wrote: > > > > I am currently involved in a number of threads, not just yours, where I > > am encouraging people to replace ambiguous returns with "return 0;". > > This is my life now. > So maybe you like this list of 160 places in which the return variable > is initialized and only used as parameter to return(The list look > good, but I haven't reviewed all 160, so there could be problems): > http://pastebin.com/5kAbCP2e Fantastic! :) These things are easy to review because if it's wrong then the compile will break. > > Does it worth doing something about those trivial cases? > > Do you have more examples of ambiguous returns, so I can help you hunt them? The main thing is what your check finds. If you know that ret is zero then return zero. regards, dan carpenter