Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932119Ab2KZVHX (ORCPT ); Mon, 26 Nov 2012 16:07:23 -0500 Received: from mail20.dotsterhost.com ([66.11.232.73]:33320 "EHLO mail20.dotsterhost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756054Ab2KZVHT (ORCPT ); Mon, 26 Nov 2012 16:07:19 -0500 X-Greylist: delayed 401 seconds by postgrey-1.27 at vger.kernel.org; Mon, 26 Nov 2012 16:07:19 EST Date: Mon, 26 Nov 2012 14:00:38 -0700 From: "Mark A. Greer" To: Mike Turquette Cc: Russ Dill , linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] Don't mark shared helper functions as inline Message-ID: <20121126210038.GA3987@animalcreek.com> References: <1353957609-1295-1-git-send-email-Russ.Dill@ti.com> <20121126195742.21126.16500@nucleus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20121126195742.21126.16500@nucleus> Organization: Animal Creek Technologies, Inc. User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1441 Lines: 33 On Mon, Nov 26, 2012 at 11:57:42AM -0800, Mike Turquette wrote: > Quoting Russ Dill (2012-11-26 11:20:09) > > The helper functions that access the opaque struct clk should > > not be marked inline since they are contained in clk.c, but expected > > to be used by other compilation units. This causes compile errors > > under gcc-4.7 > > > > In file included from arch/arm/mach-omap2/clockdomain.c:25:0: > > arch/arm/mach-omap2/clockdomain.c: In function ‘clkdm_clk_disable’: > > include/linux/clk-provider.h:338:12: error: inlining failed in call to always_inline ‘__clk_get_enable_count’: function body not available > > arch/arm/mach-omap2/clockdomain.c:1001:28: error: called from here > > make[1]: *** [arch/arm/mach-omap2/clockdomain.o] Error 1 > > make: *** [arch/arm/mach-omap2] Error 2 > > > Hi Mike. > Regardless, I'm still considering this patch. I've heard many times > that we should trust the compiler to optimize for us and some folks look > down on inlining in general. If anyone has an opinion on removing > inlines from the common clk core then please do speak up. You should take a look at "Chapter 15: The inline disease" in Documentation/CodingStyle. Mark -- -- 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/