From: "Pavel Machek" <pavel@ucw.cz>
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] v4.19-rt status
Date: Thu, 9 Jul 2020 23:10:33 +0200 [thread overview]
Message-ID: <20200709211033.GB9193@amd> (raw)
In-Reply-To: <20200702093244.GA12176@duo.ucw.cz>
[-- Attachment #1.1: Type: text/plain, Size: 886 bytes --]
Hi!
> Newest 4.19-rt kernel is currently v4.19.127-rt54. That's not good
> match for us, as -cip kernels are v4.19.128-cip28 and v4.19.130-cip29.
>
> I could do kernel based on v4.19.127-rt54 and v4.19.124-cip27, but I
> believe it makes more sense to wait for newer v4.19-rt release.
Still no new -rt release.
In April, Tom Zanussi took over 4.19-rt releases:
Apr 20 Linux 4.19.115-rt49
Apr 28 Linux 4.19.115-rt50
May 3 Linux 4.19.116-rt51
May 4 Linux 4.19.120-rt52
May 20 Linux 4.19.124-rt53
Jun 7 Linux 4.19.127-rt54
Jun 10 Linux 4.19.127-rt55
Based on past releases, I'd expect new -rt release real soon
now. Hmm. I guess easiest option is to just ask Tom ;-)... and I did
that.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 419 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4917): https://lists.cip-project.org/g/cip-dev/message/4917
Mute This Topic: https://lists.cip-project.org/mt/75254805/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-07-09 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 9:32 [cip-dev] v4.19-rt status Pavel Machek
2020-07-09 21:10 ` Pavel Machek [this message]
2020-07-13 7:50 ` Pavel Machek
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=20200709211033.GB9193@amd \
--to=pavel@ucw.cz \
--cc=cip-dev@lists.cip-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.