From: Rob Herring <robh@kernel.org>
To: Ivan Uvarov <i.uvarov@cognitivepilot.com>
Cc: Andre Przywara <andre.przywara@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Jernej Skrabec <jernej.skrabec@siol.net>,
Chen-Yu Tsai <wens@csie.org>,
devicetree@vger.kernel.org, Icenowy Zheng <icenowy@aosc.io>,
Maxime Ripard <mripard@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 3/5] dt-bindings: add compatible vendor prefix for Forlinx
Date: Thu, 8 Apr 2021 15:14:12 -0500 [thread overview]
Message-ID: <20210408201412.GA1887265@robh.at.kernel.org> (raw)
In-Reply-To: <20210407111428.3755684-4-i.uvarov@cognitivepilot.com>
On Wed, 07 Apr 2021 14:14:26 +0300, Ivan Uvarov wrote:
> Baoding Forlinx Embedded Technology Co., Ltd. is the manufacturer of the
> Allwinner R40/A40i-powered FETA40i-C SoM and the OKA40i-C dev/carrier board
> based on it.
>
> This patch adds the DT vendor prefix for Forlinx in preparation for a
> further patch, which includes a devicetree for the OKA40i-C board.
>
> Signed-off-by: Ivan Uvarov <i.uvarov@cognitivepilot.com>
>
> 1 file changed, 2 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-04-08 20:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 11:14 [PATCH v4 0/5] add devicetree for Forlinx FETA40i-C & OKA40i-C Ivan Uvarov
2021-04-07 11:14 ` [PATCH v4 1/5] ARM: dts: sun8i: r40: add /omit-if-no-ref/ to pinmux nodes for UARTs 0&3 Ivan Uvarov
2021-04-07 11:14 ` [PATCH v4 2/5] ARM: dts: sun8i: r40: add pinmux settings for MMC3 and UARTs 2,4,5&7 Ivan Uvarov
2021-04-07 11:14 ` [PATCH v4 3/5] dt-bindings: add compatible vendor prefix for Forlinx Ivan Uvarov
2021-04-08 20:14 ` Rob Herring [this message]
2021-04-07 11:14 ` [PATCH v4 4/5] dt-bindings: arm: add compatible for Forlinx OKA40i-C and FETA40i-C Ivan Uvarov
2021-04-08 20:14 ` Rob Herring
2021-04-07 11:14 ` [PATCH v4 5/5] ARM: dts: sun8i: r40: add devicetree for Forlinx FETA40i-C & OKA40i-C Ivan Uvarov
2021-04-15 8:08 ` [PATCH v4 0/5] " Maxime Ripard
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=20210408201412.GA1887265@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=andre.przywara@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=i.uvarov@cognitivepilot.com \
--cc=icenowy@aosc.io \
--cc=jernej.skrabec@siol.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).