From: Daniel Wagner <wagi@monom.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.6.4-rt3
Date: Wed, 22 Apr 2020 20:31:12 +0200 [thread overview]
Message-ID: <20200422183112.nfbxob7gv33fsqgp@beryllium.lan> (raw)
In-Reply-To: <20200422181232.a33sfm6udmy2zcvy@linutronix.de>
On Wed, Apr 22, 2020 at 08:12:32PM +0200, Sebastian Andrzej Siewior wrote:
> On 2020-04-22 19:33:59 [+0200], Daniel Wagner wrote:
> > Hi Sebastian,
>
> Hi Daniel,
>
> > On Thu, Apr 16, 2020 at 06:45:10PM +0200, Sebastian Andrzej Siewior wrote:
> > > I'm pleased to announce the v5.6.4-rt3 patch set.
> >
> > Finally solved my lab setup issue (NFS wants to use TCP per default now) and
> > all looks good. The fallout on rt-tests-migrate was a configuration bug on my
> > side. All rt-tests work and pass on my three system (Beaglebone Black 32bit,
> > RPi3 64bit and old x86_64 Core2 Duo CPU E8400 box in 64bit mode).
>
> So there is no backtrace of any kind in any configuration (bug or no
> bug)?
Correct, all tests pass and from a quick glance there are no backtraces in the
logs. IIRC, lava detects warnings and backtraces in the logs and marks them as
error.
v5.6.4-rt seems to be in a good shape as far my quick tests tell me.
next prev parent reply other threads:[~2020-04-22 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 16:45 [ANNOUNCE] v5.6.4-rt3 Sebastian Andrzej Siewior
2020-04-21 5:09 ` v5.6.4-rt3 suspend time allocation gripe Mike Galbraith
2020-04-22 17:33 ` [ANNOUNCE] v5.6.4-rt3 Daniel Wagner
2020-04-22 18:12 ` Sebastian Andrzej Siewior
2020-04-22 18:31 ` Daniel Wagner [this message]
2020-04-22 18:43 ` Sebastian Andrzej Siewior
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=20200422183112.nfbxob7gv33fsqgp@beryllium.lan \
--to=wagi@monom.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).