linux-kernel - Re: linux-next: build failure after merge of the final tree (workqueues tree related)

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 20 Jul 2010 10:42:52 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (workqueues
 tree related)

On 07/20/2010 07:10 AM, Stephen Rothwell wrote:
> Hi Tejun,
> 
> After merging the final tree, today's linux-next build (powerpc
> allnoconfig) failed like this:
> 
> kernel/workqueue.c: In function 'alloc_cwqs':
> kernel/workqueue.c:2634: error: 'CONFIG_SMP' undeclared (first use in this function)
> kernel/workqueue.c: In function 'free_cwqs':
> kernel/workqueue.c:2659: error: 'CONFIG_SMP' undeclared (first use in this function)
> 
> Caused by commit f34217977d717385a3e9fd7018ac39fade3964c0 ("workqueue:
> implement unbound workqueue").  Config symbols need to be checked for
> being defined ...

Heh, yeah, I have no idea what I was thinking.  Will fix up soon.

Thanks.

-- 
tejun
--
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/