From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
John Kacur <jkacur@redhat.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: Re: [PATCH RT 0/4] Linux 3.12.22-rt35-rc1
Date: Thu, 03 Jul 2014 15:15:29 +0200 [thread overview]
Message-ID: <1404393329.6068.2.camel@marge.simpson.net> (raw)
In-Reply-To: <20140703083908.54a82e5e@gandalf.local.home>
On Thu, 2014-07-03 at 08:39 -0400, Steven Rostedt wrote:
> On Thu, 03 Jul 2014 07:28:46 +0200
> Mike Galbraith <umgwanakikbuti@gmail.com> wrote:
>
> >
> > On Wed, 2014-07-02 at 13:14 -0400, Steven Rostedt wrote:
> > > Dear RT Folks,
> > >
> > > This is the RT stable review cycle of patch 3.12.22-rt35-rc1.
> > >
> > > Please scream at me if I messed something up. Please test the patches too.
> >
> > [PATCH RT 5/4] sched: Do not clear PF_NO_SETAFFINITY flag in select_fallback_rq() ?
> >
>
> Is that in 3.14-rt yet? I didn't see it. As with stable mainline,
> nothing goes into stable-rt until it is in -rt upstream.
Oh right, no, not yet.
-Mike
prev parent reply other threads:[~2014-07-03 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 17:14 Steven Rostedt
2014-07-02 17:14 ` [PATCH RT 1/4] Revert "migrate_disable pushd down in atomic_dec_and_spin_lock" Steven Rostedt
2014-07-02 17:14 ` [PATCH RT 2/4] timer: do not spin_trylock() on UP Steven Rostedt
2014-07-02 17:14 ` [PATCH RT 3/4] Fix latency histogram after "hrtimer: Set expiry time before switch_hrtimer_base()" Steven Rostedt
2014-07-02 17:14 ` [PATCH RT 4/4] Linux 3.12.22-rt35-rc1 Steven Rostedt
2014-07-03 5:28 ` [PATCH RT 0/4] " Mike Galbraith
2014-07-03 12:39 ` Steven Rostedt
2014-07-03 13:15 ` Mike Galbraith [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=1404393329.6068.2.camel@marge.simpson.net \
--to=umgwanakikbuti@gmail.com \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--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
Powered by JetHome