From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v2] sched: Add preempt checks in preempt_schedule() code
Date: Tue, 29 Mar 2016 12:22:20 +0200 [thread overview]
Message-ID: <20160329102220.GA3471@gmail.com> (raw)
In-Reply-To: <20160322085206.7450593b@gandalf.local.home>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 22 Mar 2016 10:09:30 +0100
> Peter Zijlstra <peterz@infradead.org> wrote:
>
> > On Mon, Mar 21, 2016 at 11:23:39AM -0400, Steven Rostedt wrote:
> > >
> > > Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
> >
> > What tree is this against? It does not apply.
>
> Hmm, my tree which is based on 4.5-rc7.
Hey, that's some ancient scheduler code base, we've had 40+ scheduler commits
since v4.5! ;-)
Thanks,
Ingo
next prev parent reply other threads:[~2016-03-29 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 15:23 [PATCH v2] sched: Add preempt checks in preempt_schedule() code Steven Rostedt
2016-03-22 9:09 ` Peter Zijlstra
2016-03-22 12:52 ` Steven Rostedt
2016-03-29 10:22 ` Ingo Molnar [this message]
2016-03-31 9:28 ` [tip:sched/core] sched/core: " tip-bot for Steven Rostedt
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=20160329102220.GA3471@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@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 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.