* Doing 4.4-cip release
@ 2022-03-21 8:35 Pavel Machek
2022-03-24 12:38 ` nobuhiro1.iwamatsu
0 siblings, 1 reply; 3+ messages in thread
From: Pavel Machek @ 2022-03-21 8:35 UTC (permalink / raw)
To: nobuhiro1.iwamatsu, cip-dev
[-- Attachment #1: Type: text/plain, Size: 656 bytes --]
Hi!
linux-4.4.y-cip tree should be up-to-date with changes from 4.9.305
and older.
I believe it may be good time to do 4.4.x release; last release
of 4.4.y-cip was at Feb 14, and 4.9.306 contains speculation fixes
that are rather intrusive... so it may be good time to test that we
did a good job on the easy changes.
We do not have 4.9-rt release to work with, so doing 4.4-rt is not
easy at the moment, and it may be good to do non-rt release, first,
anyway.
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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: Doing 4.4-cip release
2022-03-21 8:35 Doing 4.4-cip release Pavel Machek
@ 2022-03-24 12:38 ` nobuhiro1.iwamatsu
2022-03-24 19:05 ` Pavel Machek
0 siblings, 1 reply; 3+ messages in thread
From: nobuhiro1.iwamatsu @ 2022-03-24 12:38 UTC (permalink / raw)
To: pavel, cip-dev
Hi Pavel,
Thank for your work.
> -----Original Message-----
> From: Pavel Machek <pavel@denx.de>
> Sent: Monday, March 21, 2022 5:35 PM
> To: iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT)
> <nobuhiro1.iwamatsu@toshiba.co.jp>; cip-dev@lists.cip-project.org
> Subject: Doing 4.4-cip release
>
> Hi!
>
> linux-4.4.y-cip tree should be up-to-date with changes from 4.9.305 and older.
>
> I believe it may be good time to do 4.4.x release; last release of 4.4.y-cip was at
> Feb 14, and 4.9.306 contains speculation fixes that are rather intrusive... so it
> may be good time to test that we did a good job on the easy changes.
I see.
BTW, linux-4.4.y-st tree, do you have any idea to have a git tag? When merging into cip tree,
I think the tags make it easier to manage. For example, create a tag the string contained in
localversion-st file.
>
> We do not have 4.9-rt release to work with, so doing 4.4-rt is not easy at the
> moment, and it may be good to do non-rt release, first, anyway.
>
OK, I will prepare for the release.
Best regards,
Nobuhiro
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Doing 4.4-cip release
2022-03-24 12:38 ` nobuhiro1.iwamatsu
@ 2022-03-24 19:05 ` Pavel Machek
0 siblings, 0 replies; 3+ messages in thread
From: Pavel Machek @ 2022-03-24 19:05 UTC (permalink / raw)
To: nobuhiro1.iwamatsu; +Cc: pavel, cip-dev
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
Hi!
> > linux-4.4.y-cip tree should be up-to-date with changes from 4.9.305 and older.
> >
> > I believe it may be good time to do 4.4.x release; last release of 4.4.y-cip was at
> > Feb 14, and 4.9.306 contains speculation fixes that are rather intrusive... so it
> > may be good time to test that we did a good job on the easy changes.
>
> I see.
> BTW, linux-4.4.y-st tree, do you have any idea to have a git tag? When merging into cip tree,
> I think the tags make it easier to manage. For example, create a tag the string contained in
> localversion-st file.
Good idea. I pushed the tag, v4.4-st5 . (I plan to keep the tag in
sync with 4.9: 4.9.30X should correspond to v4.4-stX).
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-03-24 19:05 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-03-21 8:35 Doing 4.4-cip release Pavel Machek
2022-03-24 12:38 ` nobuhiro1.iwamatsu
2022-03-24 19:05 ` Pavel Machek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox