Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751872AbbKZM5c (ORCPT ); Thu, 26 Nov 2015 07:57:32 -0500 Received: from verein.lst.de ([213.95.11.211]:35738 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750943AbbKZM5a (ORCPT ); Thu, 26 Nov 2015 07:57:30 -0500 Date: Thu, 26 Nov 2015 13:57:27 +0100 From: Torsten Duwe To: Denis Kirjanov Cc: Steven Rostedt , Michael Ellerman , Jiri Kosina , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, live-patching@vger.kernel.org Subject: Re: [PATCH v4 1/9] ppc64 (le): prepare for -mprofile-kernel Message-ID: <20151126125727.GA6484@lst.de> References: <20151125172608.9588569260@newverein.lst.de> <20151125172855.49E3469260@newverein.lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 747 Lines: 20 On Thu, Nov 26, 2015 at 01:12:12PM +0300, Denis Kirjanov wrote: > On 11/25/15, Torsten Duwe wrote: > > + */ > > + return 2; > I didn't find where you check for this return value. That's a pure debugging convenience. The return test is for != 0, so any non-zero value will do. I've encountered situations where I'd really liked to know _why_ a routine failed/succeeded, visible in the registers in the debugger. This is no big thing, I have no strong opinion about this. Torsten -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/