From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Walleij Subject: Re: linux-next: Tree for Feb 17 (pinctrl-msm) Date: Tue, 25 Feb 2014 10:39:46 +0100 Message-ID: References: <20140217172329.2c61499f57842ec2ed177bc5@canb.auug.org.au> <530247FC.90606@infradead.org> <20140224174646.GA32621@sonymobile.com> <530B8C15.50100@infradead.org> <20140224184120.GB18563@joshc.qualcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: In-Reply-To: <20140224184120.GB18563@joshc.qualcomm.com> Sender: linux-kernel-owner@vger.kernel.org To: Josh Cartwright , Thomas Gleixner , Grant Likely Cc: Randy Dunlap , Bjorn Andersson , Stephen Rothwell , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-msm@vger.kernel.org" List-Id: linux-arm-msm@vger.kernel.org On Mon, Feb 24, 2014 at 7:41 PM, Josh Cartwright wrote: > On Mon, Feb 24, 2014 at 10:14:45AM -0800, Randy Dunlap wrote: > 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. > > Whether or not this is intentional is not clear. Do we support modules > installing chained irq handlers? That is a good question to tglx/Grant ... As the kernel looks today, drivers installing chained handlers cannot be modules, and that is it. Yours, Linus Walleij