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: Doing 4.4-cip release
Date: Thu, 24 Mar 2022 20:05:35 +0100	[thread overview]
Message-ID: <20220324190535.GA6144@duo.ucw.cz> (raw)
In-Reply-To: <TYAPR01MB62522189BBBBAE46DEA125DD92199@TYAPR01MB6252.jpnprd01.prod.outlook.com>

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

      reply	other threads:[~2022-03-24 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 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=20220324190535.GA6144@duo.ucw.cz \
    --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