From: "Nobuhiro Iwamatsu" <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <pavel@denx.de>
Cc: <cip-dev@lists.cip-project.org>, <jan.kiszka@siemens.com>,
<SZ.Lin@moxa.com>, <ben.hutchings@codethink.co.uk>,
<Chris.Paterson2@renesas.com>
Subject: Re: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15
Date: Thu, 8 Oct 2020 05:32:13 +0000 [thread overview]
Message-ID: <OSBPR01MB29838595D7430E92E750A188920B0@OSBPR01MB2983.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20201007201102.GB32003@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
Hi Pavel,
> -----Original Message-----
> From: Pavel Machek [mailto:pavel@denx.de]
> Sent: Thursday, October 8, 2020 5:11 AM
> To: iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ) <nobuhiro1.iwamatsu@toshiba.co.jp>
> Cc: cip-dev@lists.cip-project.org; pavel@denx.de; jan.kiszka@siemens.com; SZ.Lin@moxa.com;
> ben.hutchings@codethink.co.uk; Chris.Paterson2@renesas.com
> Subject: Re: [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15
>
> Hi!
>
> > FYI:
> > https://patchwork.ozlabs.org/project/netdev/patch/20200922072931.2148-1-geert+renesas@glider.be/
> >
>
> Yes, and the revert is now queued to 4.19-stable, too.
>
> So.. what do we want to do here?
>
> We can merge 4.19.151 to -cip when it is released, and I can then
> release new -cip-rt that works on renesas boards...
Yes, I think so.
Perhaps 4.19.151 will be released this weekend. And this week is the release week of the CIP kernel.
And I think we can use it to release the cip-rt tree.
>
> Best regards,
> Pavel
Best regards,
Nobuhiro
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5506): https://lists.cip-project.org/g/cip-dev/message/5506
Mute This Topic: https://lists.cip-project.org/mt/77295090/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]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2020-10-08 5:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 9:06 [cip-dev] [ANNOUNCE] v4.19.148-cip35-rt15 Pavel Machek
2020-10-04 20:29 ` Chris Paterson
2020-10-04 21:39 ` Pavel Machek
2020-10-06 6:49 ` Nobuhiro Iwamatsu
[not found] ` <163B547D5FFC3079.30511@lists.cip-project.org>
2020-10-06 23:43 ` Nobuhiro Iwamatsu
2020-10-07 20:11 ` Pavel Machek
2020-10-08 5:32 ` Nobuhiro Iwamatsu [this message]
2020-10-08 5:45 ` Nobuhiro 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=OSBPR01MB29838595D7430E92E750A188920B0@OSBPR01MB2983.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=Chris.Paterson2@renesas.com \
--cc=SZ.Lin@moxa.com \
--cc=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--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).