Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752920AbaBXSq6 (ORCPT ); Mon, 24 Feb 2014 13:46:58 -0500 Received: from merlin.infradead.org ([205.233.59.134]:47365 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752421AbaBXSq5 (ORCPT ); Mon, 24 Feb 2014 13:46:57 -0500 Message-ID: <530B9399.5010909@infradead.org> Date: Mon, 24 Feb 2014 10:46:49 -0800 From: Randy Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Josh Cartwright , Thomas Gleixner CC: Bjorn Andersson , Linus Walleij , Stephen Rothwell , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , linux-arm-msm@vger.kernel.org Subject: Re: linux-next: Tree for Feb 17 (pinctrl-msm) References: <20140217172329.2c61499f57842ec2ed177bc5@canb.auug.org.au> <530247FC.90606@infradead.org> <20140224174646.GA32621@sonymobile.com> <530B8C15.50100@infradead.org> <20140224184120.GB18563@joshc.qualcomm.com> In-Reply-To: <20140224184120.GB18563@joshc.qualcomm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/24/2014 10:41 AM, Josh Cartwright wrote: > On Mon, Feb 24, 2014 at 10:14:45AM -0800, Randy Dunlap wrote: >> On 02/24/2014 09:46 AM, Bjorn Andersson wrote: >>> On Mon 24 Feb 06:46 PST 2014, Linus Walleij wrote: >>>> On Mon, Feb 17, 2014 at 6:33 PM, Randy Dunlap wrote: >>>>> On 02/16/2014 10:23 PM, Stephen Rothwell wrote: >>>>> ERROR: "handle_bad_irq" [drivers/pinctrl/pinctrl-msm.ko] undefined! >>>> >>>> Weird, Bj?rn do you know what may be causing this? >>> >>> I include linux/irq.h to get hold of handle_bad_irq() and as far as I can see >>> there are no changes related to that in linux-next. >>> >>> Do we know if the build still fails? Or if something changed? >>> >>> >>> Please let me know if I should pull down the -next tree and try to reproduce >>> this. >> >> I guess that you get off free on this one since I didn't post the failing >> .config file and I have already deleted it. >> >> I'm trying to reproduce it now but it's slow going. I'll let you know if >> I get it to fail again. > > Without too much effort, I can get this to fail just by making > CONFIG_PINCTRL_MSM=m. handle_bad_irq isn't marked EXPORT_SYMBOL*, so > hence the warning. Yes, I was just about to write the same thing. > Whether or not this is intentional is not clear. Do we support modules > installing chained irq handlers? Thomas? > For now, the patch below just makes this driver 'bool' instead of > 'tristate'. What does pinctrl have against using loadable modules in many cases? > Josh > > --8<-- > Subject: [PATCH] pinctrl: msm: make PINCTRL_MSM bool instead of tristate > > Modular builds of pinctrl-msm break due to handle_bad_irq being > unexported for module use. For now, make PINCTRL_MSM 'bool'. > > Signed-off-by: Josh Cartwright > --- > drivers/pinctrl/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig > index be361b7..1e4e693 100644 > --- a/drivers/pinctrl/Kconfig > +++ b/drivers/pinctrl/Kconfig > @@ -217,7 +217,7 @@ config PINCTRL_IMX28 > select PINCTRL_MXS > > config PINCTRL_MSM > - tristate > + bool > select PINMUX > select PINCONF > select GENERIC_PINCONF > -- ~Randy -- 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/