From: Steven Rostedt <rostedt@goodmis.org>
To: Tim Sander <tim@krieglstein.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>
Subject: Re: [PATCH RT 0/5] Linux 3.4.69-rt86-rc1
Date: Mon, 2 Dec 2013 09:40:39 -0500 [thread overview]
Message-ID: <20131202094039.620fb42c@gandalf.local.home> (raw)
In-Reply-To: <1720233.5xc8N19PWk@dabox>
On Mon, 02 Dec 2013 14:32:13 +0100
Tim Sander <tim@krieglstein.org> wrote:
> > If all goes well, this patch will be converted to the next main release
> > on 11/25/2013.
> I don't want to nag you but as this date is in the past i just wanted to know
> if anything has not gone well besides that the non-rc version is not
> available? Which would be just a "cosmetic" issue.
Nope, all went well, I just got side tracked by other things needing to
get done by Turkey day. Thanks for the reminder.
I'll push these out today.
-- Steve
prev parent reply other threads:[~2013-12-02 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 18:41 [PATCH RT 0/5] Linux 3.4.69-rt86-rc1 Steven Rostedt
2013-11-21 18:42 ` [PATCH RT 1/5] genirq: Set the irq thread policy without checking CAP_SYS_NICE Steven Rostedt
2013-11-21 18:42 ` [PATCH RT 2/5] hwlat-detector: Dont ignore threshold module parameter Steven Rostedt
2013-11-21 18:42 ` [PATCH RT 3/5] mm/memcontrol: Dont call schedule_work_on in preemption disabled context Steven Rostedt
2013-11-21 18:42 ` [PATCH RT 4/5] drm: remove preempt_disable() from drm_calc_vbltimestamp_from_scanoutpos() Steven Rostedt
2013-11-21 18:42 ` [PATCH RT 5/5] Linux 3.4.69-rt86-rc1 Steven Rostedt
2013-12-02 13:32 ` [PATCH RT 0/5] " Tim Sander
2013-12-02 14:40 ` Steven Rostedt [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=20131202094039.620fb42c@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=tglx@linutronix.de \
--cc=tim@krieglstein.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 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).