From: Daniel Wagner <wagi@monom.org>
To: Pavel Machek <pavel@denx.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Julia Cartwright <julia@ni.com>
Subject: Re: [ANNOUNCE] 4.4.206-rt190
Date: Sat, 21 Dec 2019 11:49:15 +0100 [thread overview]
Message-ID: <e2256c5e-826b-3046-de15-7c2599b1444c@monom.org> (raw)
In-Reply-To: <20191216132724.GA22097@amd>
Hi Pavel,
Sorry for the delay.
On 16.12.19 14:27, Pavel Machek wrote:
> Hi!
>
>> I'm pleased to announce the 4.4.206-rt190 stable release.
>>
>> This release is just an update to the new stable 4.4.206 version
>> and no RT specific changes have been made.
>
> Thanks!
>
> I'm getting failures with one of our configs:
>
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/380509098
> https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/103388506
>
> This failure is not new, we have been working around it for a
> while. It can be fixed using:
>
> git cherry-pick 8409299
>
> https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/103395886
>
> (If you prefer, I can submit patch via email).
We should route this patch via stable. I'll send out the request to
Greg. Just a sec.
Thanks,
Daniel
prev parent reply other threads:[~2019-12-21 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 10:47 [ANNOUNCE] 4.4.206-rt190 Daniel Wagner
2019-12-16 13:27 ` Pavel Machek
2019-12-21 10:49 ` Daniel Wagner [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=e2256c5e-826b-3046-de15-7c2599b1444c@monom.org \
--to=wagi@monom.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@denx.de \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.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;
as well as URLs for NNTP newsgroup(s).