From: Jonathan Schwender <schwenderjonathan@gmail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: v5.10.14-rt28 fails to build without CONFIG_SMP
Date: Sun, 14 Feb 2021 11:54:27 +0100 [thread overview]
Message-ID: <ae545d99-66ec-ef32-604e-ee5caee8ece5@gmail.com> (raw)
In-Reply-To: <20210209180601.hbjpgfcntgsjirbk@linutronix.de>
Hi Sebastian,
It seems that commit 17cfc9697f5574e4b523c21fca160aac5a3ac6dc "softirq:
Update the WIP"
breaks builds without CONFIG_SMP, due to unresolved references to
tasklet_unlock and tasklet_unlock_wait in softirq.c
In include/linux/interrupt.h the functions are declared if either
CONFIG_SMP or CONFIG_PREEMPT_RT are defined.
However, in softirq.c the functions are now only in an #ifdef CONFIG_SMP
block.
Regards
Jonathan Schwender
next prev parent reply other threads:[~2021-02-14 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 18:06 [ANNOUNCE] v5.10.14-rt28 Sebastian Andrzej Siewior
2021-02-14 10:54 ` Jonathan Schwender [this message]
2021-02-16 8:29 ` v5.10.14-rt28 fails to build without CONFIG_SMP Sebastian Andrzej Siewior
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=ae545d99-66ec-ef32-604e-ee5caee8ece5@gmail.com \
--to=schwenderjonathan@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.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).