From: "Chris Paterson" <chris.paterson2@renesas.com>
To: Pavel Machek <pavel@denx.de>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"SZ.Lin@moxa.com" <SZ.Lin@moxa.com>,
"ben.hutchings@codethink.co.uk" <ben.hutchings@codethink.co.uk>
Subject: Re: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15
Date: Sun, 4 Oct 2020 20:29:49 +0000 [thread overview]
Message-ID: <TYAPR01MB23984E9AECF0CDEE4B32B7F1B70F0@TYAPR01MB2398.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20201004090653.GA18130@amd>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
Hello Pavel,
> From: Pavel Machek <pavel@denx.de>
> Sent: 04 October 2020 10:07
>
> *** gpg4o | The signature of this email could not be verified because the
> following public key is missing. Click here to search and import the key
> 30E7F06A95DBFAF2 ***
>
> Hi!
>
> New realtime trees should be available at kernel.org.
>
> Trees are available at
>
> https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-
> cip.git/log/?h=linux-4.19.y-cip-rt
> https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-
> cip.git/log/?h=linux-4.19.y-cip-rt-rebase
>
> And their content should be identical.
Thank you for the release.
>
> This patch merges 4.19.148-stable into -cip-rt (because that's what
> recent -rt is based on, and older -rt tree is too old). Unfortunately,
> that brings regression with ethernet on Renesas Arm64 targets, which
> will prevent boot, and fail tests etc.
>
> Kernel that should work ok on Renesas Arm64 machines can be obtained
> by reverting fb3a780e7a76cf8efb055f8322ec039923cee41f "ravb: Fixed to
> be able to unload modules" on top of -cip-rt release.
So we're releasing a Kernel that we know doesn't boot on one of CIP's reference platforms?
Or did you already revert the above patch as part of your release?
Thanks, Chris
>
> Best regards,
> Pavel
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures)
> http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5497): https://lists.cip-project.org/g/cip-dev/message/5497
Mute This Topic: https://lists.cip-project.org/mt/77295090/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-10-04 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 9:06 [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15 Pavel Machek
2020-10-04 20:29 ` Chris Paterson [this message]
2020-10-04 21:39 ` Pavel Machek
2020-10-06 6:49 ` Nobuhiro Iwamatsu
[not found] ` <163B547D5FFC3079.30511@lists.cip-project.org>
2020-10-06 23:43 ` Nobuhiro Iwamatsu
2020-10-07 20:11 ` Pavel Machek
2020-10-08 5:32 ` Nobuhiro Iwamatsu
2020-10-08 5:45 ` Nobuhiro Iwamatsu
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=TYAPR01MB23984E9AECF0CDEE4B32B7F1B70F0@TYAPR01MB2398.jpnprd01.prod.outlook.com \
--to=chris.paterson2@renesas.com \
--cc=SZ.Lin@moxa.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=pavel@denx.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).