linux-kernel - Re: [-next July 21] s390 build failure : kernel/workqueue.o

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]

Message-ID: <4C47F0EC.5040507@petalogix.com>
Date:	Thu, 22 Jul 2010 09:19:08 +0200
From:	Michal Simek <michal.simek@...alogix.com>
To:	Sachin Sant <sachinp@...ibm.com>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	Tejun Heo <tj@...nel.org>,
	Martin Schwidefsky <schwidefsky@...ibm.com>
Subject: Re: [-next July 21] s390 build failure : kernel/workqueue.o

Sachin Sant wrote:
> Today's next fails to build on a s390 box with
> 
>  CC      kernel/workqueue.o
> kernel/workqueue.c: In function 'init_workqueues':
> kernel/workqueue.c:3525: error: negative width in bit-field '<anonymous>'
> make[1]: *** [kernel/workqueue.o] Error 1
> 
> Yesterday's next was good.
> The following patches added/changed the BUILD_BUG_ON() statement.
> 
> bdbc5dd7de5d07d6c9d3536e598956165a031d4c
>        workqueue: prepare for WQ_UNBOUND implementation
> 7a22ad757ec75186ad43a5b4670fa7423ee8f480
>         workqueue: carry cpu number in work data once execution starts
> 
> I have gcc version 4.3.2 installed on the system.

the same problem on microblaze gcc 4.1.2.

Thanks,
Michal



-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
--
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/