From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@elte.hu>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/s390: fix compile error in sched/core.c
Date: Wed, 11 Jan 2012 10:17:00 +0100 [thread overview]
Message-ID: <4F0D538C.5040202@de.ibm.com> (raw)
In-Reply-To: <1326272868.2442.122.camel@twins>
On 11/01/12 10:07, Peter Zijlstra wrote:
> On Wed, 2012-01-11 at 08:58 +0100, Christian Borntraeger wrote:
>> From: Christian Borntraeger <borntraeger@de.ibm.com>
>>
>> commit 029632fbb7b7c9d85063cc9eb470de6c54873df3
>> sched: Make separate sched*.c translation units
>>
>> removed the include of asm/mutex.h from sched.c. This breaks the combination of
>>
>> CONFIG_MUTEX_SPIN_ON_OWNER=yes
>> CONFIG_HAVE_ARCH_MUTEX_CPU_RELAX=yes
>> like s390 without mutex debugging:
>>
>> CC kernel/sched/core.o
>> kernel/sched/core.c: In function ‘mutex_spin_on_owner’:
>> kernel/sched/core.c:3287: error: implicit declaration of function ‘arch_mutex_cpu_relax’
>> make[2]: *** [kernel/sched/core.o] Error 1
>>
>> Lets re-add the include to kernel/sched/core.c
>
> Weird, I would have expected -next to pick this up..
Maybe the builds of next runs with DEBUG_MUTEXES, which disables MUTEX_SPIN_ON_OWNER.
> Anyway, no objection although do we really need that extra #ifdef ?
Dont think so. I consider this more as a comment why we need this. Whoever applies the patch,
feel free to remove the ifdefs.
Christian
next prev parent reply other threads:[~2012-01-11 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 7:58 [PATCH] sched/s390: fix compile error in sched/core.c Christian Borntraeger
2012-01-11 9:07 ` Peter Zijlstra
2012-01-11 9:17 ` Christian Borntraeger [this message]
2012-01-18 9:33 ` Christian Borntraeger
2012-01-24 10:04 ` Peter Zijlstra
2012-01-26 20:26 ` [tip:sched/urgent] sched/s390: Fix " tip-bot for Christian Borntraeger
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=4F0D538C.5040202@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=schwidefsky@de.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.