From: Corey Minyard <cminyard@mvista.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>, minyard@acm.org
Cc: linux-rt-users@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] sched: Fix compile warning when using CONFIG_PREEMPT_NONE
Date: Fri, 29 Jul 2016 12:49:31 -0500 [thread overview]
Message-ID: <579B972B.3050409@mvista.com> (raw)
In-Reply-To: <20160729154602.GF21715@linutronix.de>
On 07/29/2016 10:46 AM, Sebastian Andrzej Siewior wrote:
> * minyard@acm.org | 2016-06-29 11:55:11 [-0500]:
>
>> From: Corey Minyard <cminyard@mvista.com>
>>
>> preemptible_lazy() is only used under CONFIG_PREEMPT, but it was
>> always defined. Move it into a CONFIG_PREEMPT ifdef.
> Oh sorry, I missed that one but the problem is gone, right?
>
> Sebastian
Yes, it appears to be gone. Before I think you could define
CONFIG_PREEMPT_LAZY
without CONFIG_PREEMPT being defined.
-corey
prev parent reply other threads:[~2016-07-29 17:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 16:55 [PATCH] sched: Fix compile warning when using CONFIG_PREEMPT_NONE minyard
2016-07-29 15:46 ` Sebastian Andrzej Siewior
2016-07-29 17:49 ` Corey Minyard [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=579B972B.3050409@mvista.com \
--to=cminyard@mvista.com \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=minyard@acm.org \
--cc=rostedt@goodmis.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 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.