From: Steven Rostedt <rostedt@goodmis.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: Linux RT 4.14 Merge conflict
Date: Tue, 31 Jul 2018 11:30:13 -0400 [thread overview]
Message-ID: <20180731113013.12306761@gandalf.local.home> (raw)
In-Reply-To: <41428b93-b272-c052-57f9-3bf4daf23b03@ti.com>
On Tue, 31 Jul 2018 08:18:00 -0500
Dan Murphy <dmurphy@ti.com> wrote:
> Do you have a time frame of when we will get the update?
I'm starting the merges today, and depending on how testing goes, I
hope to have a release this week.
-- Steve
prev parent reply other threads:[~2018-07-31 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 20:25 Linux RT 4.14 Merge conflict Dan Murphy
2018-07-23 20:59 ` Steven Rostedt
2018-07-23 20:59 ` Dan Murphy
2018-07-31 13:18 ` Dan Murphy
2018-07-31 15:30 ` 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=20180731113013.12306761@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=dmurphy@ti.com \
--cc=linux-rt-users@vger.kernel.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