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: <CACRpkda7Q4q5YoWHbvC-gkcE99h0nUr3QhFT+GGuLGA4=V9gqg@mail.gmail.com>
Date:	Fri, 28 Oct 2011 21:32:37 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Axel Lin <axel.lin@...il.com>, Marc Zyngier <marc.zyngier@....com>
Cc:	linux-kernel@...r.kernel.org,
	Rob Herring <rob.herring@...xeda.com>,
	"Stephen Rothwell sfr"@canb.auug.org.au
Subject: Re: [linux-next 20111025] build failure with make u8500_defconfig

On Thu, Oct 27, 2011 at 5:11 AM, Axel Lin <axel.lin@...il.com> wrote:

> I got below build error by "make u8500_defconfig" on linux-next 20111025.
>
>  CC      arch/arm/common/gic.o
> arch/arm/common/gic.c: In function 'gic_dist_init':
> arch/arm/common/gic.c:290: error: 'irq_start' undeclared (first use in this function)
> arch/arm/common/gic.c:290: error: (Each undeclared identifier is reported only once
> arch/arm/common/gic.c:290: error: for each function it appears in.)
> arch/arm/common/gic.c:296: error: 'struct gic_chip_data' has no member named 'irq_offset'
> arch/arm/common/gic.c: In function 'gic_init':
> arch/arm/common/gic.c:620: error: 'THIS_MODULE' undeclared (first use in this function)
> make[1]: *** [arch/arm/common/gic.o] Error 1
> make: *** [arch/arm/common] Error 2

Hm I don't get it, the lines in the compile error seems to come from the
"ARM: gic: consolidate PPI handling" patch, so Marc if this is my
fault can you help me out in advicing me on how to fix it up properly?

Yours,
Linus Walleij
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ