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]
Date:	Wed, 12 Oct 2011 15:24:51 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Tomoya MORINAGA <tomoya-linux@....lapis-semi.com>
Cc:	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,

On Tue, 11 Oct 2011 16:02:40 +0900 Tomoya MORINAGA <tomoya-linux@....lapis-semi.com> wrote:
>
> (2011/10/11 15:37), Stephen Rothwell wrote:
> > 
> > On Thu, 6 Oct 2011 14:48:26 +1100 Stephen Rothwell<sfr@...b.auug.org.au>  wrote:
> >>
> >> After merging the gpio tree, today's linux-next build (x86_64
> >> allmodconfig) failed like this:
> >>
> >> ERROR: "irq_setup_generic_chip" [drivers/gpio/gpio-pch.ko] undefined!
> >> ERROR: "irq_alloc_generic_chip" [drivers/gpio/gpio-pch.ko] undefined!
> >> ERROR: "irq_setup_generic_chip" [drivers/gpio/gpio-ml-ioh.ko] undefined!
> >> ERROR: "irq_alloc_generic_chip" [drivers/gpio/gpio-ml-ioh.ko] undefined!
> >>
> >> Presumably caused by commits 54be566317b6 ("gpio-ml-ioh: Support
> >> interrupt function") and 38eb18a6f92d ("gpio-pch: Support interrupt
> >> function").
> >>
> >> I have used the gpio tree from next-20111005 for today.
> > 
> > I am still getting this build failure.
> > 
> I built this driver with success using linux-3.0.
> I want to try to build with the same as your build environment.
> Where can I get your environment ?

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).

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ