From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Adam Ford <aford173@gmail.com>, linux-renesas-soc@vger.kernel.org
Cc: aford@beaconembedded.com,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/2] dt-bindings: arm: renesas: Document beacon-rzg2m
Date: Wed, 15 Jul 2020 11:16:43 +0300 [thread overview]
Message-ID: <c2e52f87-b2cf-ca36-7780-5e206f065d40@cogentembedded.com> (raw)
In-Reply-To: <20200714123419.3390-2-aford173@gmail.com>
Hello!
On 14.07.2020 15:34, Adam Ford wrote:
> Beacon EmbeddedWorks in introducing a development kit based on the
s/in/is/?
> Renesas RZ/G2M platform. This patch adds the entry to the bindings
> list.
>
> Signed-off-by: Adam Ford <aford173@gmail.com>
> ---
> V2: New to series
>
> diff --git a/Documentation/devicetree/bindings/arm/renesas.yaml b/Documentation/devicetree/bindings/arm/renesas.yaml
> index d8fd25bccbf5..0d4dabb4a164 100644
> --- a/Documentation/devicetree/bindings/arm/renesas.yaml
> +++ b/Documentation/devicetree/bindings/arm/renesas.yaml
> @@ -118,6 +118,7 @@ properties:
> items:
> - enum:
> - hoperun,hihope-rzg2m # HopeRun HiHope RZ/G2M platform
> + - beacon,beacon-rzg2m # Beacon EmbeddedWorks RZ/G2M Kit
Why the vendor-prefixes.yaml file calls it Compass Electronics Group?
[...]
MBR, Sergei
next prev parent reply other threads:[~2020-07-15 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 12:34 [PATCH V2 1/2] arm64: dts: Introduce r8a774a1-beacon-rzg2m-kit Adam Ford
2020-07-14 12:34 ` [PATCH V2 2/2] dt-bindings: arm: renesas: Document beacon-rzg2m Adam Ford
2020-07-15 8:16 ` Sergei Shtylyov [this message]
2020-07-15 8:32 ` Geert Uytterhoeven
2020-07-15 8:58 ` Geert Uytterhoeven
2020-07-15 13:27 ` Adam Ford
2020-07-15 13:37 ` Geert Uytterhoeven
2020-07-15 8:53 ` [PATCH V2 1/2] arm64: dts: Introduce r8a774a1-beacon-rzg2m-kit Geert Uytterhoeven
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=c2e52f87-b2cf-ca36-7780-5e206f065d40@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=robh+dt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®