From: Sachin Sant <sachinp@in.ibm.com>
To: linux-s390@vger.kernel.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Tejun Heo <tj@kernel.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: [-next July 21] s390 build failure : kernel/workqueue.o
Date: Wed, 21 Jul 2010 16:10:35 +0530 [thread overview]
Message-ID: <4C46CEA3.7040503@in.ibm.com> (raw)
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.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next reply other threads:[~2010-07-21 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 10:40 Sachin Sant [this message]
2010-07-21 15:57 ` [-next July 21] s390 build failure : kernel/workqueue.o Tejun Heo
2010-07-22 5:49 ` Sachin Sant
2010-07-22 9:25 ` Martin Schwidefsky
2010-07-22 12:25 ` [PATCH wq#for-next] workqueue: fix how cpu number is stored in work->data Tejun Heo
2010-07-22 15:10 ` Martin Schwidefsky
2010-07-22 20:41 ` Tejun Heo
2010-07-22 20:13 ` Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C46CEA3.7040503@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).