From: "Lad Prabhakar" <prabhakar.mahadev-lad.rj@bp.renesas.com>
To: "nobuhiro1.iwamatsu@toshiba.co.jp"
<nobuhiro1.iwamatsu@toshiba.co.jp>,
"pavel@denx.de" <pavel@denx.de>
Cc: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [cip-dev] [PATCH v2 4.4.y-cip 00/11] Renesas RZ/G1x add SoC detection support
Date: Thu, 3 Dec 2020 08:55:27 +0000 [thread overview]
Message-ID: <OSBPR01MB5048174358C54D8549D9AE5FAAF20@OSBPR01MB5048.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <OSBPR01MB298357DC462CE3BB01390EC592F20@OSBPR01MB2983.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
Hi Nobuhiro, Pavel,
> -----Original Message-----
> From: nobuhiro1.iwamatsu@toshiba.co.jp <nobuhiro1.iwamatsu@toshiba.co.jp>
> Sent: 03 December 2020 02:29
> To: pavel@denx.de; Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Cc: cip-dev@lists.cip-project.org; Biju Das <biju.das.jz@bp.renesas.com>
> Subject: RE: [PATCH v2 4.4.y-cip 00/11] Renesas RZ/G1x add SoC detection support
>
> Hi,
>
> > -----Original Message-----
> > From: Pavel Machek [mailto:pavel@denx.de]
> > Sent: Tuesday, December 1, 2020 6:28 PM
> > To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> > Cc: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 □ＳＷＣ◯ＡＣＴ)
> > <nobuhiro1.iwamatsu@toshiba.co.jp>; Pavel Machek <pavel@denx.de>; Biju Das
> <biju.das.jz@bp.renesas.com>
> > Subject: Re: [PATCH v2 4.4.y-cip 00/11] Renesas RZ/G1x add SoC detection support
> >
> > Hi!
> >
> > > This patch series adds SoC detection support for Renesas RZ/G1x SoC's.
> > >
> > > All the patches apart from {7, 9, 11}/11 have been cherry picked from
> > > Linux v5.10-rc6
> >
> > Series looks good to me, I can apply it if there are no other
> > comments.
>
> I applied and pushed this series.
>
Thank you for the review and acceptance.
Cheers,
Prabhakar
> Best regards,
> Nobuhiro
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5935): https://lists.cip-project.org/g/cip-dev/message/5935
Mute This Topic: https://lists.cip-project.org/mt/78628858/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]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2020-12-03 8:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 8:39 [cip-dev] [PATCH v2 4.4.y-cip 00/11] Renesas RZ/G1x add SoC detection support Lad Prabhakar
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 01/11] base: soc: Early register bus when needed Lad Prabhakar
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 02/11] dt-bindings: arm: renesas: Convert 'renesas,prr' to json-schema Lad Prabhakar
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 03/11] soc: renesas: Identify SoC and register with the SoC bus Lad Prabhakar
2020-12-01 9:21 ` Pavel Machek
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 04/11] ARM: dts: r8a7743: Add device node for PRR Lad Prabhakar
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 05/11] ARM: dts: r8a7745: " Lad Prabhakar
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 06/11] soc: renesas: Identify RZ/G1N Lad Prabhakar
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 07/11] ARM: dts: r8a7744: Add device node for PRR Lad Prabhakar
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 08/11] soc: renesas: Identify RZ/G1H Lad Prabhakar
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 09/11] ARM: dts: r8a7742: Add device node for PRR Lad Prabhakar
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 10/11] soc: renesas: Identify RZ/G1C Lad Prabhakar
2020-12-01 8:39 ` [cip-dev] [PATCH v2 4.4.y-cip 11/11] ARM: dts: r8a77470: Add device node for PRR Lad Prabhakar
2020-12-01 9:28 ` [cip-dev] [PATCH v2 4.4.y-cip 00/11] Renesas RZ/G1x add SoC detection support Pavel Machek
2020-12-03 2:28 ` Nobuhiro Iwamatsu
2020-12-03 8:55 ` Lad Prabhakar [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=OSBPR01MB5048174358C54D8549D9AE5FAAF20@OSBPR01MB5048.jpnprd01.prod.outlook.com \
--to=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.