From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Dan Murphy <dmurphy@ti.com>
Cc: 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>,
rostedt@goodmis.org, "Hernandez, Carlos" <ceh@ti.com>,
"Strashko, Grygorii" <grygorii.strashko@ti.com>
Subject: Re: Linux stable vs RT stable and RT dev
Date: Fri, 9 Feb 2018 20:30:16 +0100 [thread overview]
Message-ID: <20180209193015.wms4o7wxsi3t535g@linutronix.de> (raw)
In-Reply-To: <a1c7a58e-2d67-f6fd-6e91-9cbd03678e7d@ti.com>
On 2018-02-09 12:59:43 [-0600], Dan Murphy wrote:
> Sebastian
HI Dan,
> Hmmm I wonder why the compiler does not complain about this warning then.
>
> I will look into it. This warning has been around for a while (4.9-rt as well).
probably once the local_irq_save() was removed.
> We also noticed that there are 2 merge conflicts when going to 4.14.18.
> Any comments about providing a merge conflict email to the list?
I am not sure about how helpful this actually is. Usually I do a RT
release a week while I have stuff in my pipe. Currently Greg is
releasing a lot. On the other hand it is almost two weeks since my last
release.
> Attached is the merge conflicts we are seeing 4.14.15-> 4.14.18
In meantime I already uploaded the patch queue for v4.14.18-rt14.
I plan to sync with Steven's tracing then release -rt15 probably later
today.
> Dan
Sebastian
next prev parent reply other threads:[~2018-02-09 19:30 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
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 [this message]
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=20180209193015.wms4o7wxsi3t535g@linutronix.de \
--to=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=rostedt@goodmis.org \
--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