From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-rt-users@vger.kernel.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH RT] sched: drop is_special_task_state() check from __set_current_state_no_track()
Date: Wed, 1 Aug 2018 17:53:08 +0200 [thread overview]
Message-ID: <20180801155308.wcw6mo6mrhlsgpg3@linutronix.de> (raw)
In-Reply-To: <20180801091942.46292953@gandalf.local.home>
On 2018-08-01 09:19:42 [-0400], Steven Rostedt wrote:
> I don't think we need to keep the do { } while with a single line. It
> is now equivalent to the non-debug version of __set_current_state()
> which is defined as:
>
> #define __set_current_state(state_value) \
> current->state = (state_value)
okay.
> -- Steve
Sebastian
prev parent reply other threads:[~2018-08-01 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 9:05 [PATCH RT] sched: drop is_special_task_state() check from __set_current_state_no_track() Sebastian Andrzej Siewior
2018-08-01 13:19 ` Steven Rostedt
2018-08-01 15:53 ` Sebastian Andrzej Siewior [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=20180801155308.wcw6mo6mrhlsgpg3@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).