archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <>
To: Tejun Heo <>
Subject: linux-next: build failure after merge of the workqueues tree
Date: Thu, 17 Feb 2011 14:33:21 +1100	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 821 bytes --]

Hi Tejun,

After merging the workqueues tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

kernel/workqueue.c: In function 'init_workqueues':
kernel/workqueue.c:3780: error: 'WQ_FREEZEABLE' undeclared (first use in this function)

Caused by commit 58a69cb47ec6991bf006a3e5d202e8571b0327a4 ("workqueue,
freezer: unify spelling of 'freeze' + 'able' to 'freezable'") being
mismerged with commit 4149efb22da66e326fc48baf80d628834509f7f0
("workqueue: add system_freezeable_wq") which added another use of

Please do at least simple build testing before submitting to
linux-next ...

I have used the version of the workqueues tree from next-20110216 for
Stephen Rothwell          

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2011-02-17  3:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17  3:33 Stephen Rothwell [this message]
2011-02-17  9:23 ` linux-next: build failure after merge of the workqueues tree Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2017-11-02  3:34 Stephen Rothwell
2017-11-03 13:59 ` Tejun Heo
2015-06-20 10:26 Stephen Rothwell
2011-02-18  3:57 Stephen Rothwell
2011-02-18  9:07 ` Tejun Heo
2011-02-21  2:27 ` Stephen Rothwell
2011-02-21  5:48   ` Dmitry Torokhov
2011-02-09  4:12 Stephen Rothwell
2011-02-09  8:37 ` Tejun Heo

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).