From: Steven Rostedt <rostedt@goodmis.org>
To: Dan Murphy <dmurphy@ti.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
William Mills <wmills@ti.com>, Julia Cartwright <julia@ni.com>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"Nori, Sekhar" <nsekhar@ti.com>, "Hernandez, Carlos" <ceh@ti.com>,
"Strashko, Grygorii" <grygorii.strashko@ti.com>
Subject: Re: Linux stable vs RT stable and RT dev
Date: Tue, 6 Feb 2018 11:17:18 -0500 [thread overview]
Message-ID: <20180206111718.0eb267da@gandalf.local.home> (raw)
In-Reply-To: <8e201971-d626-7ef6-addd-bbbc32f63770@ti.com>
On Tue, 6 Feb 2018 09:47:15 -0600
Dan Murphy <dmurphy@ti.com> wrote:
> This is where we can put an automated job in place to merge GKH rc
> stable into the RT branch and report only upcoming merge conflicts.
> Then no one actually has to report or ask it would just be assumed?
I'd be careful about this. There's a few (not many) subtle changes that
get backported to stable that can break RT. You wont be able to notice
it with compiling, but it can cause deadlocks in certain scenarios.
-- Steve
next prev parent reply other threads:[~2018-02-06 16:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 19:00 Linux stable vs RT stable and RT dev Mills, William
2018-02-02 21:46 ` Julia Cartwright
2018-02-03 1:20 ` William Mills
2018-02-05 21:17 ` Dan Murphy
2018-02-06 14:34 ` Sebastian Andrzej Siewior
2018-02-06 15:47 ` Dan Murphy
2018-02-06 16:17 ` Steven Rostedt [this message]
2018-02-06 20:07 ` Dan Murphy
2018-02-09 17:39 ` Sebastian Andrzej Siewior
2018-02-09 18:59 ` Dan Murphy
2018-02-09 19:30 ` Sebastian Andrzej Siewior
2018-02-09 19:43 ` Dan Murphy
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=20180206111718.0eb267da@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=ceh@ti.com \
--cc=dmurphy@ti.com \
--cc=grygorii.strashko@ti.com \
--cc=julia@ni.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=wmills@ti.com \
/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