All of lore.kernel.org
 help / color / mirror / Atom feed
From: iwamatsu@nigauri.org (Nobuhiro Iwamatsu)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [PATCH 1/9] arm64: dts: renesas: r8a774c0: Add secondary CA53 CPU core
Date: Thu, 11 Apr 2019 18:34:49 +0900	[thread overview]
Message-ID: <CABMQnVJ5d_cBFwdihc8KfKUEh2cSA_OHptDB_A9v99pt7d-HYA@mail.gmail.com> (raw)
In-Reply-To: <OSBPR01MB210351DFE8721A24FA116F50B82F0@OSBPR01MB2103.jpnprd01.prod.outlook.com>

Hi, Biju.

2019?4?11?(?) 15:55 Biju Das <biju.das@bp.renesas.com>:
>
>
> Hi Nobuhiro-San,
>
> Thanks for the feedback.
>
> Regards,
> Biju
>
> > -----Original Message-----
> > From: nobuhiro1.iwamatsu at toshiba.co.jp
> > <nobuhiro1.iwamatsu@toshiba.co.jp>
> > Sent: 11 April 2019 00:14
> > To: Biju Das <biju.das@bp.renesas.com>; cip-dev at lists.cip-project.org
> > Subject: RE: [cip-dev] [PATCH 1/9] arm64: dts: renesas: r8a774c0: Add
> > secondary CA53 CPU core
> >
> > Hi, Diju.
> >
> > > -----Original Message-----
> > > From: cip-dev-bounces at lists.cip-project.org
> > > [mailto:cip-dev-bounces at lists.cip-project.org] On Behalf Of Biju Das
> > > Sent: Friday, March 22, 2019 6:19 PM
> > > To: cip-dev at lists.cip-project.org
> > > Cc: Biju Das <biju.das@bp.renesas.com>
> > > Subject: [cip-dev] [PATCH 1/9] arm64: dts: renesas: r8a774c0: Add
> > > secondary CA53 CPU core
> > >
> > > From: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> > >
> > > Add a device node for the second Cortex-A53 CPU core on the Renesas
> > > RZ/G2E (a.k.a r8a774c0) SoC, and adjust the interrupt delivery masks
> > > for the ARM Generic Interrupt Controller and Architectured Timer.
> >
> > I think that 'Architected Timer' is correct, not 'Architectured Timer'.
> > If my point is correct, I will fix and apply the commit message.
> >
> > Other patches are looks good to me.
>
> I believe it is correct. see the link below.
>
> https://www.kernel.org/doc/Documentation/devicetree/bindings/arm/arch_timer.txt
>
> Already the cherry-picked patch from upstream is reviewed by wider people.
> So I believe it is not good to change the commit messages or ordering of patches.
>
> We have upstreamed RZ/G2[ME] patches in specific order. So we expect the same order in cip kernel as well.
> Like SoC definitions,SYSC,RST,CLK,Pinctrl , SoC DTSI,Board DTSI and the rest of the drivers.
>
> We may be wrong. So please correct us if we are wrong.

I do not intend to change the patch application order.
However, since our CIP kernel needs to be maintained on a long-term,
I think it is better to fix the problems that we noticed and include the
corrected content in the commit message.

>
> Regards,
> Biju

Best regards,
  Nobuhiro

  parent reply	other threads:[~2019-04-11  9:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22  9:19 [cip-dev] [PATCH 0/9] Add SMP/INTC-EX/PFC/GPIO support Biju Das
2019-03-22  9:19 ` [cip-dev] [PATCH 1/9] arm64: dts: renesas: r8a774c0: Add secondary CA53 CPU core Biju Das
2019-04-10 23:14   ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-04-11  6:54     ` Biju Das
2019-04-11  6:59       ` Biju Das
2019-04-11  9:34       ` Nobuhiro Iwamatsu [this message]
2019-03-22  9:19 ` [cip-dev] [PATCH 2/9] pinctrl: sh-pfc: rcar: Rename automotive-only arrays to automotive Biju Das
2019-03-22  9:19 ` [cip-dev] [PATCH 3/9] pinctrl: sh-pfc: r8a77990: Add INTC-EX pins, groups and function Biju Das
2019-03-22  9:19 ` [cip-dev] [PATCH 4/9] arm64: dts: renesas: r8a774c0: Add INTC-EX device node Biju Das
2019-03-22  9:19 ` [cip-dev] [PATCH 5/9] arm64: dts: renesas: r8a774c0: Add PFC support Biju Das
2019-03-22  9:19 ` [cip-dev] [PATCH 6/9] dt-bindings: gpio: rcar: Add r8a774a1 (RZ/G2M) support Biju Das
2019-03-22  9:19 ` [cip-dev] [PATCH 7/9] dt-bindings: gpio: rcar: Add r8a774c0 (RZ/G2E) support Biju Das
2019-03-22  9:19 ` [cip-dev] [PATCH 8/9] arm64: dts: renesas: r8a774c0: Add GPIO device nodes Biju Das
2019-03-22  9:19 ` [cip-dev] [PATCH 9/9] arm64: dts: renesas: r8a774c0-cat874: Add pincontrol support to scif2 Biju Das

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=CABMQnVJ5d_cBFwdihc8KfKUEh2cSA_OHptDB_A9v99pt7d-HYA@mail.gmail.com \
    --to=iwamatsu@nigauri.org \
    --cc=cip-dev@lists.cip-project.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 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.