[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20160113102738.GA29964@linutronix.de>
Date: Wed, 13 Jan 2016 11:27:38 +0100
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: kbuild test robot <fengguang.wu@...el.com>
Cc: Thomas Gleixner <tglx@...utronix.de>, kbuild-all@...org,
David Howells <dhowells@...hat.com>,
Richard Kuo <rkuo@...eaurora.org>,
linux-kernel@...r.kernel.org,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-m68k@...ts.linux-m68k.org
Subject: Re: [linux-rt-devel:for-kbuild-bot/prepare-release 32/256] warning:
(DEBUG_ATOMIC_SLEEP) selects PREEMPT_COUNT which has unmet direct
dependencies (COLDFIRE)
* kbuild test robot | 2015-12-24 09:57:43 [+0800]:
>All warnings (new ones prefixed by >>):
>
>warning: (DEBUG_ATOMIC_SLEEP) selects PREEMPT_COUNT which has unmet direct dependencies (COLDFIRE)
The situation slightly changed. Before the patch in question:
|warning: (PREEMPT && DEBUG_ATOMIC_SLEEP) selects PREEMPT_COUNT which has unmet direct dependencies (COLDFIRE)
so it is just s@...EMPT@...EMPT_COUNT@.
This pops up because DEBUG_ATOMIC_SLEEP can be selected while
kernel/Kconfig.preempt has not been included into Kconfig. This warning
is not limited to m68k but should also pop up on alpha / frv and hexagon.
Those architectures don't include kernel/Kconfig.preempt at all.
Is this something that should be fixed?
Sebastian
Powered by blists - more mailing lists