linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build warning after merge of the workqueues tree
Date: Tue, 19 Mar 2013 14:58:04 +1100	[thread overview]
Message-ID: <20130319145804.7af0b995413adb35d16992ef@canb.auug.org.au> (raw)

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

Hi Tejun,

After merging the workqueues tree, today's linux-next build (powerpc
allnoconfig) produced this warning:

kernel/workqueue.c:260:13: warning: 'workqueue_freezing' defined but not used [-Wunused-variable]

Introduced by commit 699ce097efe8 ("workqueue: implement and use
pwq_adjust_max_active()").  This build does not have CONFIG_FREEZER set.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

             reply	other threads:[~2013-03-19  3:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19  3:58 Stephen Rothwell [this message]
2013-03-19 21:01 ` [PATCH wq/for-3.10] workqueue: define workqueue_freezing static variable iff CONFIG_FREEZER Tejun Heo
2023-01-13  3:31 linux-next: build warning after merge of the workqueues tree Stephen Rothwell
2023-01-13 16:31 ` Tejun Heo
2023-01-13 16:47   ` Valentin Schneider
2023-01-13 16:48     ` Valentin Schneider
2023-01-13 17:16       ` Tejun Heo
2024-01-30  2:37 Stephen Rothwell
2024-04-21 23:48 ` Stephen Rothwell
2024-04-22 19:59   ` Tejun Heo
2024-04-22 20:13   ` Tejun Heo
2024-02-09  3:24 Stephen Rothwell
2024-02-09  3:45 ` Waiman Long
2024-02-16  3:00 Stephen Rothwell
2024-02-16  4:46 ` 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:
  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=20130319145804.7af0b995413adb35d16992ef@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).