From: "Pavel Machek" <pavel@denx.de>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
Pavel Machek <pavel@denx.de>,
"nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: [cip-dev] Patches that need porting from 4.19 to 5.10-cip tree
Date: Tue, 22 Jun 2021 13:57:15 +0200 [thread overview]
Message-ID: <20210622115715.GA12826@duo.ucw.cz> (raw)
In-Reply-To: <OSZPR01MB6877A74A6479B7870A3211F0B7099@OSZPR01MB6877.jpnprd01.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1073 bytes --]
Hi!
> > *** gpg4o | HINT: Error while checking message with detached signature
> > (PGP/MIME signature)!
> > Couldn't locate the original MIME source of the mail to verify the signature!
> > gpg4oh32.dll:: func_IV Init OK ***
> >
> > Hi!
> >
> > Here is the list of patches that are in 4.19-cip but not yet in
> > 5.10... according to my scripting.
>
> Prabhakar has reviewed your list and has submitted all of the relevant patches in his "Renesas RZ/G2 sync patches from 4.19-cip to 5.10-cip" series [0].
>
> Attached is a spreadsheet that summarises his analysis.
> As you can see there are a lot of patches that are already present in v5.10, and some aren't needed.
> There are a few patches marked as "Don't care". This is from a Renesas/RZ/G point of view. They should probably still be looked into by someone in CIP.
>
Thanks for doing this, let me take a look.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 428 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6572): https://lists.cip-project.org/g/cip-dev/message/6572
Mute This Topic: https://lists.cip-project.org/mt/83254843/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2021-06-22 11:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 10:04 [cip-dev] Patches that need porting from 4.19 to 5.10-cip tree Pavel Machek
2021-06-22 10:32 ` Chris Paterson
2021-06-22 11:57 ` Pavel Machek [this message]
2021-06-22 12:47 ` Pavel Machek
2021-06-22 13:26 ` Lad Prabhakar
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=20210622115715.GA12826@duo.ucw.cz \
--to=pavel@denx.de \
--cc=Chris.Paterson2@renesas.com \
--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;
as well as URLs for NNTP newsgroup(s).