linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Daniel Wagner <wagi@monom.org>
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>, Pavel Machek <pavel@denx.de>
Subject: Re: [ANNOUNCE] 4.4.206-rt190
Date: Mon, 16 Dec 2019 14:27:24 +0100	[thread overview]
Message-ID: <20191216132724.GA22097@amd> (raw)
In-Reply-To: <20191206104701.CC686500518@mail.monom.org>

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

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).

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2019-12-16 13:27 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 [this message]
2019-12-21 10:49   ` Daniel Wagner

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=20191216132724.GA22097@amd \
    --to=pavel@denx.de \
    --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=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tom.zanussi@linux.intel.com \
    --cc=wagi@monom.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).