public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: nobuhiro1.iwamatsu@toshiba.co.jp
Cc: pavel@denx.de, cip-dev@lists.cip-project.org
Subject: Re: Coordintaing -rt releases in May
Date: Tue, 10 May 2022 15:01:53 +0200	[thread overview]
Message-ID: <20220510130153.GA20410@amd> (raw)
In-Reply-To: <TYWPR01MB94203CED9AB8DD767CF5614D92C69@TYWPR01MB9420.jpnprd01.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 810 bytes --]

Hi!

> > It is time to do -rt update but I don't see good match in releases:
> > 
> > 5.10.109-rt65
> > 5.10.112-cip6
> 
> We have released v5.10.109-cip5.

Ok, I created 5.10.109-based -rt release.

> > 
> > 4.19.240-rt108
> > 4.19.239-cip72
> > 
> > It may make sense to delay or do extra releases to get matches.
> 
> The latest release of 4.19.y is 4.19.241, but we could release CIP
> kernel based on 4.19.240.

I believe that would be rather "strange". I could do
4.19.240-rt108-cip72 based release, but I guess it will be better to
wait for next 4.19-rt and do a matching -cip release.

Thanks 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 --]

       reply	other threads:[~2022-05-10 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220509120033.GA25149@duo.ucw.cz>
     [not found] ` <TYWPR01MB94203CED9AB8DD767CF5614D92C69@TYWPR01MB9420.jpnprd01.prod.outlook.com>
2022-05-10 13:01   ` Pavel Machek [this message]
2022-05-13  7:41     ` Coordintaing -rt releases in May nobuhiro1.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=20220510130153.GA20410@amd \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    /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