From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>
Cc: <pavel@denx.de>, <Chris.Paterson2@renesas.com>,
<masashi.kudo@cybertrust.co.jp>,
<masami.ichikawa@cybertrust.co.jp>
Subject: [cip-dev] [ANNOUNCE] Release v4.4.277-cip60
Date: Tue, 3 Aug 2021 04:30:34 +0000 [thread overview]
Message-ID: <TYAPR01MB62521F8D2A41BC0B6DEEDE3F92F09@TYAPR01MB6252.jpnprd01.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Hi,
CIP kernel team has released Linux kernel v4.4.277-cip60.
The 4.4.y tree was scheduled to be released next week, but we have
rescheduled it for the release of the CIP-RT tree.
The linux-4.4.y-cip tree has been updated base version from v4.4.274
to v4.4.277. No CIP-specific patches have been added to this version.
You can get this release via the git tree at:
v4.4.277-cip60:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
branch:
linux-4.4.y-cip
commit hash:
6012d2c32efa70a548d6e59b763c39bb0d38f2e0
added commits:
CIP: Bump version suffix to -cip60 after merge from stable
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
[-- Attachment #2: Type: text/plain, Size: 429 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6647): https://lists.cip-project.org/g/cip-dev/message/6647
Mute This Topic: https://lists.cip-project.org/mt/84632315/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]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2021-08-03 4:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 4:30 Nobuhiro Iwamatsu [this message]
2021-08-03 19:53 ` [cip-dev] [ANNOUNCE] Release v4.4.277-cip60 Pavel Machek
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=TYAPR01MB62521F8D2A41BC0B6DEEDE3F92F09@TYAPR01MB6252.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=masami.ichikawa@cybertrust.co.jp \
--cc=masashi.kudo@cybertrust.co.jp \
--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).