From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <cip-dev@lists.cip-project.org>
Cc: <masashi.kudo@cybertrust.co.jp>, <ben.hutchings@codethink.co.uk>,
<chris.paterson2@renesas.com>, <wens@csie.org>, <SZ.Lin@moxa.com>,
<pavel@denx.de>
Subject: [cip-dev] [ANNOUNCE] Release v4.19.140-cip33
Date: Sat, 22 Aug 2020 22:38:44 +0000 [thread overview]
Message-ID: <OSBPR01MB29836C57F77EA897BB72E1F592580@OSBPR01MB2983.jpnprd01.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
Hi all,
CIP kernel team has released Linux kernel v4.19.140-cip33.
The linux-4.19.y-cip tree has been updated base version from v4.19.138
to v4.19.140, and the fix about DRM is added.
You can get this release via the git tree at:
v4.19.140-cip33:
repository:
https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
branch:
linux-4.19.y-cip
commit hash:
03cdb749e6350f0403badbf7931e420ea7514f56
added commits:
CIP: Bump version suffix to -cip33 after merge from stable
drm: atomic helper: fix W=1 warnings
drm: Add drm_atomic_get_old/new_private_obj_state
drm: of: Fix linking when CONFIG_OF is not set
Best regards,
Nobuhiro
[-- Attachment #2: Type: text/plain, Size: 419 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5227): https://lists.cip-project.org/g/cip-dev/message/5227
Mute This Topic: https://lists.cip-project.org/mt/76356608/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
reply other threads:[~2020-08-22 22:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=OSBPR01MB29836C57F77EA897BB72E1F592580@OSBPR01MB2983.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=SZ.Lin@moxa.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=chris.paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=masashi.kudo@cybertrust.co.jp \
--cc=pavel@denx.de \
--cc=wens@csie.org \
/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).