From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tomoya MORINAGA Subject: Re: linux-next: build failure after merge of the gpio tree Date: Wed, 12 Oct 2011 14:29:16 +0900 Message-ID: <4E9525AC.9080909@dsn.lapis-semi.com> References: <20111006144826.a69a5ea59d4ca94f8f7414cf@canb.auug.org.au> <20111011173714.d54bbcee6c0676ddcc37a1f3@canb.auug.org.au> <4E93EA10.4030405@dsn.lapis-semi.com> <20111012152451.66ce5ddffb4c5b3a4f6a31cf@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Return-path: Received: from sm-d311v.smileserver.ne.jp ([203.211.202.206]:19352 "EHLO sm-d311v.smileserver.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751071Ab1JLF3W (ORCPT ); Wed, 12 Oct 2011 01:29:22 -0400 In-Reply-To: <20111012152451.66ce5ddffb4c5b3a4f6a31cf@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell , Grant Likely Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Tomoya MORINAGA Hi, Stephen (2011/10/12 13:24), Stephen Rothwell wrote: > > Just try building gpio-pch and gpio-ml-ioh as modules ... > irq_setup_generic_chip() does not have an EXPORT_SYMBOL (and didn't in > v3.0 either). > Your report looks like the same as ours. In our develop environment, build becomes success only gpio-pch/gpio-ml-ioh is integrated as built-in. In case of integrated as modules, build becomes failure. I understood this behavior is specification/limitation of GPIO interrupt function. Is it true ? -- tomoya ROHM Co., Ltd.