From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Tejun Heo <tj@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the workqueues tree
Date: Fri, 16 Feb 2024 14:00:14 +1100 [thread overview]
Message-ID: <20240216140014.4842449a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
Hi all,
After merging the workqueues tree, today's linux-next build (x86_64
allnoconfig) produced this warning:
WARNING: unmet direct dependencies detected for IRQ_WORK
Depends on [n]: SMP [=n]
Selected by [y]:
- PRINTK [=y]
- PERF_EVENTS [=y] && HAVE_PERF_EVENTS [=y]
Other allnoconfig builds produced similar warnings.
Introduced by commit
9d6efa8d0dd0 ("workqueue, irq_work: Build fix for !CONFIG_IRQ_WORK")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-02-16 3:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 3:00 Stephen Rothwell [this message]
2024-02-16 4:46 ` linux-next: build warning after merge of the workqueues tree Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2024-02-09 3:24 Stephen Rothwell
2024-02-09 3:45 ` Waiman Long
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
2023-01-13 3:31 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
2013-03-19 3:58 Stephen Rothwell
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=20240216140014.4842449a@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).