linux-kernel - Re: linux-next: build failure after merge of the gpio tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABMQnV+S2WbW0YZBiMXfs81b2dyLzj9wBxPmNuFrYErKfXsWtg@mail.gmail.com>
Date:	Wed, 12 Oct 2011 16:21:00 +0900
From:	Nobuhiro Iwamatsu <iwamatsu@...auri.org>
To:	Tomoya MORINAGA <tomoya-linux@....lapis-semi.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Grant Likely <grant.likely@...retlab.ca>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Tomoya MORINAGA <tomoya-linux@....okisemi.com>
Subject: Re: linux-next: build failure after merge of the gpio tree

Hi,

2011年10月12日14:29 Tomoya MORINAGA <tomoya-linux@....lapis-semi.com>:
> 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 ?
>

This is a problem of generic-chip.
I created the patch and contributed the point to LKML.
He forgot to put you into CC, sorry.

Please check LKML for subject of "[PATCH] irq: Add EXPORT_SYMBOL to
function of irq generic-chip".

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/