cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <pavel@denx.de>, <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] 4.4.277-rt224 released
Date: Sat, 31 Jul 2021 22:22:09 +0000	[thread overview]
Message-ID: <TYAPR01MB62529CA5354B848A0EDC6BFC92ED9@TYAPR01MB6252.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20210730102632.GA3234@duo.ucw.cz>

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

Hi Pavel,

> -----Original Message-----
> From: Pavel Machek [mailto:pavel@denx.de]
> Sent: Friday, July 30, 2021 7:27 PM
> To: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ) <nobuhiro1.iwamatsu@toshiba.co.jp>
> Subject: 4.4.277-rt224 released
> 
> Hi!
> 
> 4.4.277-rt224 is out, and it would be useful to do -cip-rt release
> based on that. Would it be possible to do -cip release based on
> 4.4.277?

Yes, 4.4.y will be released on the second Friday, but we can reschedule it for the cip-rt tree.
4.4.277 has been tested by auto-merge and auto-test and can be released.

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/344049911

So, I will prepare for the release.

Best regards,
  Nobuhiro

[-- Attachment #2: Type: text/plain, Size: 429 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6645): https://lists.cip-project.org/g/cip-dev/message/6645
Mute This Topic: https://lists.cip-project.org/mt/84547413/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/10495289/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


      reply	other threads:[~2021-07-31 22:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 10:26 [cip-dev] 4.4.277-rt224 released Pavel Machek
2021-07-31 22:22 ` Nobuhiro Iwamatsu [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=TYAPR01MB62529CA5354B848A0EDC6BFC92ED9@TYAPR01MB6252.jpnprd01.prod.outlook.com \
    --to=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=cip-dev@lists.cip-project.org \
    --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).