From: Pavel Machek <pavel@denx.de>
To: nobuhiro1.iwamatsu@toshiba.co.jp
Cc: cip-dev@lists.cip-project.org, florian.bezdeka@siemens.com,
pavel@denx.de, masami.ichikawa@cybertrust.co.jp,
jan.kiszka@siemens.com, Chris.Paterson2@renesas.com,
uli@fpond.eu
Subject: Re: [cip-dev] [ANNOUNCE] Release v4.19.259-cip82 and v5.10.145-cip17
Date: Fri, 30 Sep 2022 10:41:02 +0200 [thread overview]
Message-ID: <20220930084101.GA13099@amd> (raw)
In-Reply-To: <TYWPR01MB9420DF3BE19B60B7CCFAA25792549@TYWPR01MB9420.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
Hi!
> > > > The linux-4.19.y-cip tree has been updated base version from
> > > > v4.19.257 to v4.19.259, and the linux-5.10.y-cip tree has been
> > > > updated base version from
> > > > v5.10.140 to v5.10.145.
...
> Right, I forgot to push to repository...
> I pushed yesterday afternoon (14:00 JST), so it is updated.
I see the updates now.
There's good match of v5.10.145-cip17, v5.10.145-rt74, I'll likely get
advantage of that.
On 4.19 side, last -rt is Aug 13, Linux 4.19.255-rt113. I'd like
matchig -cip release when next 4.19-rt is released.
Thank you and 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 --]
prev parent reply other threads:[~2022-09-30 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 8:09 [ANNOUNCE] Release v4.19.259-cip82 and v5.10.145-cip17 nobuhiro1.iwamatsu
2022-09-26 13:05 ` [cip-dev] " Bezdeka, Florian
2022-09-26 13:23 ` Pavel Machek
2022-09-28 2:19 ` nobuhiro1.iwamatsu
2022-09-30 8:41 ` Pavel Machek [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=20220930084101.GA13099@amd \
--to=pavel@denx.de \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=masami.ichikawa@cybertrust.co.jp \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=uli@fpond.eu \
/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