From: Hanks Chen <hanks.chen@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <wsd_upstream@mediatek.com>
Subject: Re: [PATCH 1/1] dt-bindings: cpu: Add a support cpu type for cortex-a75
Date: Mon, 16 Mar 2020 15:46:30 +0800 [thread overview]
Message-ID: <1584344790.29731.1.camel@mtkswgap22> (raw)
In-Reply-To: <f1b8239a-a68f-bd50-585e-26109850a1fc@gmail.com>
On Sun, 2020-03-15 at 19:44 +0100, Matthias Brugger wrote:
> Thanks for your patch.
>
> On 15/03/2020 16:08, Hanks Chen wrote:
> > [Detail]
>
> This line is not needed.
got it, will fix it. Thanks for reviewing.
>
> > Add arm cpu type cortex-a75.
> >
> > Change-Id: I2b05948915acfa6a04a0b8fa88684a12b6d5c2ca
>
> No Change-Id in upstream kernel patches please.
>
got it, will fix it. Thanks for reviewing.
> > Signed-off-by: Hanks Chen <hanks.chen@mediatek.com>
> > ---
> > Documentation/devicetree/bindings/arm/cpus.yaml | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/Documentation/devicetree/bindings/arm/cpus.yaml b/Documentation/devicetree/bindings/arm/cpus.yaml
> > index c23c24f..51b75f7 100644
> > --- a/Documentation/devicetree/bindings/arm/cpus.yaml
> > +++ b/Documentation/devicetree/bindings/arm/cpus.yaml
> > @@ -128,6 +128,7 @@ properties:
> > - arm,cortex-a57
> > - arm,cortex-a72
> > - arm,cortex-a73
> > + - arm,cortex-a75
> > - arm,cortex-m0
> > - arm,cortex-m0+
> > - arm,cortex-m1
> >
>
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2020-03-16 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 15:08 [PATCH 1/1] dt-bindings: cpu: Add a support cpu type for cortex-a75 Hanks Chen
2020-03-15 18:44 ` Matthias Brugger
2020-03-16 7:46 ` Hanks Chen [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=1584344790.29731.1.camel@mtkswgap22 \
--to=hanks.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wsd_upstream@mediatek.com \
/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).