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, 21 Dec 2011 13:24:30 +0100
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	"Cousson, Benoit" <b-cousson@...com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (mfd
 tree related)

Hi Benoit,

On Wed, Dec 21, 2011 at 11:51:27AM +0100, Cousson, Benoit wrote:
> Hi Stephen,
> 
> On 12/21/2011 7:33 AM, Stephen Rothwell wrote:
> >Hi all,
> >
> >After merging the final tree, today's linux-next build (powerpc
> >allyesconfig) failed like this:
> >
> >drivers/mfd/twl-core.c: In function 'twl_probe':
> >drivers/mfd/twl-core.c:1212:22: error: 'TWL6030_IRQ_BASE' undeclared (first use in this function)
> >drivers/mfd/twl-core.c:1212:22: note: each undeclared identifier is reported only once for each function it appears in
> >drivers/mfd/twl-core.c:1213:39: error: 'TWL6030_BASE_NR_IRQS' undeclared (first use in this function)
> >drivers/mfd/twl-core.c:1215:22: error: 'TWL4030_IRQ_BASE' undeclared (first use in this function)
> >drivers/mfd/twl-core.c:1216:39: error: 'TWL4030_BASE_NR_IRQS' undeclared (first use in this function)
> >drivers/mfd/twl-core.c:1218:3: error: implicit declaration of function 'irq_domain_add_simple' [-Werror=implicit-function-declaration]
> >
> >Caused by commit 4eea8b1d717d ("mfd: Add initial DT support for
> >twl4030/twl6030").  A missing include?  Or a CONFIG problem?
> 
> Both in fact...
> 
> There are some nasty dependencies with that TWL driver and the IRQ
> defined in OMAP headers only. I was fooled by the name of these
> macros.
> I naively thought this could be fixed later as written in the
> comment I added. I appears this is not the case :-(.
> 
> >This build does not have CONFIG_IRQ_DOMAIN set.
> 
> Ooops, I was not aware of that domain CONFIG. That one is an easy fix.
> 
> 
> Samuel,
> 
> Just let me know if you will have time for an updated version before Xmas.
I have time to merge an updated version, yes.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
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