From: Ingo Molnar <mingo@kernel.org>
To: Juri Lelli <juri.lelli@gmail.com>
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/2] A couple of sched patches
Date: Tue, 11 Feb 2014 09:49:56 +0100 [thread overview]
Message-ID: <20140211084956.GB26063@gmail.com> (raw)
In-Reply-To: <1392107067-19907-1-git-send-email-juri.lelli@gmail.com>
* Juri Lelli <juri.lelli@gmail.com> wrote:
> This two patches (on top of tip/master as of today) fix bugs
> in sched/core. First one is a repost of
> http://comments.gmane.org/gmane.linux.kernel/1638425, and exposed,
> at least to me, another bug (fixed by second patch).
With today's -tip there's a new warning on UP builds:
/home/mingo/tip/kernel/sched/deadline.c:993: warning: 'pull_dl_task' declared 'static' but never defined
And in general the #ifdef happiness of deadline.c is rather sad:
comet:~/tip> grep '#ifdef' kernel/sched/deadline.c
#ifdef CONFIG_SMP
#ifdef CONFIG_SMP
#ifdef CONFIG_SMP
#ifdef CONFIG_SMP
#ifdef CONFIG_SMP
#ifdef CONFIG_SMP
#ifdef CONFIG_SCHED_HRTICK
#ifdef CONFIG_SMP
#ifdef CONFIG_SCHED_HRTICK
#ifdef CONFIG_SMP
#ifdef CONFIG_SCHED_HRTICK
#ifdef CONFIG_SMP
#ifdef CONFIG_SMP
#ifdef CONFIG_SMP
#ifdef CONFIG_SMP
#ifdef CONFIG_SMP
All that needs to be cleaned up.
Thanks,
Ingo
prev parent reply other threads:[~2014-02-11 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 8:24 Juri Lelli
2014-02-11 8:24 ` [REPOST - PATCH 1/2] sched/core: fix sched_rt_global_validate Juri Lelli
2014-02-21 20:31 ` [tip:sched/urgent] sched/core: Fix sched_rt_global_validate tip-bot for Juri Lelli
2014-02-11 8:24 ` [PATCH 2/2] sched/core: make dl_b->lock IRQ safe Juri Lelli
2014-02-21 20:32 ` [tip:sched/urgent] sched/core: Make " tip-bot for Juri Lelli
2014-02-11 8:49 ` Ingo Molnar [this message]
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=20140211084956.GB26063@gmail.com \
--to=mingo@kernel.org \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome