From: Steven Rostedt <rostedt@goodmis.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
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>, John Kacur <jkacur@redhat.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
stable-rt@vger.kernel.org
Subject: Re: [PATCH RT 3/6] rt: Make cpu_chill() use hrtimer instead of msleep()
Date: Fri, 7 Mar 2014 09:52:23 -0500 [thread overview]
Message-ID: <20140307095223.2f412a1a@gandalf.local.home> (raw)
In-Reply-To: <531996BB.2050401@linutronix.de>
On Fri, 07 Mar 2014 10:51:55 +0100
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> On 03/05/2014 01:33 AM, Steven Rostedt wrote:
> > 3.2.55-rt79-rc1 stable review patch.
> > If anyone has any objections, please let me know.
>
> Now that you posted "cpu_chill: Add a UNINTERRUPTIBLE
> hrtimer_nanosleep" wouldn't it make sense to delay this patches from
> the stable series until we get them all in one go?
Sure, say this on the day I'm about to release ;-)
Nah, I'll release these today anyway. Otherwise I can't update to the
mainline stables. When the rc candidates are out, it holds up any new
updates to the versions.
Also, the stable 3.10 has this bug already. Might as well update all
the stables with the same fix. It makes it easier on my side, as the
way I do the updates is to use the same quilt queue for all releases. I
start with 3.10, and get them working, and then apply the same queue to
3.8. Any conflicts in the patch I do a quilt fork, with a -v3.8
appended, and then after getting that working I go to 3.4, and so on.
This also lets me drop patches that are not applicable for earlier
releases.
If I delay this for a new update, then 3.10 will be out of sync. I'm
just going to release these, and then we can start a new one right away.
Thanks!
-- Steve
next prev parent reply other threads:[~2014-03-07 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 0:33 [PATCH RT 0/6] Linux 3.2.55-rt79-rc1 Steven Rostedt
2014-03-05 0:33 ` [PATCH RT 1/6] rcutree/rcu_bh_qs: disable irq while calling rcu_preempt_qs() Steven Rostedt
2014-03-05 0:33 ` [PATCH RT 2/6] Revert "x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT" Steven Rostedt
2014-03-05 0:33 ` [PATCH RT 3/6] rt: Make cpu_chill() use hrtimer instead of msleep() Steven Rostedt
2014-03-07 9:51 ` Sebastian Andrzej Siewior
2014-03-07 14:52 ` Steven Rostedt [this message]
2014-03-07 15:23 ` Sebastian Andrzej Siewior
2014-03-05 0:33 ` [PATCH RT 4/6] kernel/hrtimer: be non-freezeable in cpu_chill() Steven Rostedt
2014-03-05 0:33 ` [PATCH RT 5/6] arm/unwind: use a raw_spin_lock Steven Rostedt
2014-03-05 0:33 ` [PATCH RT 6/6] Linux 3.2.55-rt79-rc1 Steven Rostedt
-- strict thread matches above, loose matches on Subject: below --
2014-03-05 0:29 [PATCH RT 0/6] Linux 3.4.82-rt101-rc1 Steven Rostedt
2014-03-05 0:29 ` [PATCH RT 3/6] rt: Make cpu_chill() use hrtimer instead of msleep() 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=20140307095223.2f412a1a@gandalf.local.home \
--to=rostedt@goodmis.org \
--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=stable-rt@vger.kernel.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).