From: Rob Herring <robh+dt@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Andy Gross <agross@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v2 1/4] dt-bindings: vendor-prefixes: Add Longcheer Technology Co., Ltd.
Date: Mon, 22 Jul 2019 09:12:20 -0600 [thread overview]
Message-ID: <CAL_Jsq+Fe+bExtqXRHNoEvATh3qVuDBnS0SqgSJenZs+yDVOOQ@mail.gmail.com> (raw)
In-Reply-To: <20190722092211.100586-2-stephan@gerhold.net>
On Mon, Jul 22, 2019 at 3:24 AM Stephan Gerhold <stephan@gerhold.net> wrote:
>
> Add the "longcheer" vendor prefix for Longcheer Technology Co., Ltd.,
> an "industry-leading service provider of mobile phone design
> and product delivery". (http://www.longcheer.com)
>
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-07-22 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 9:22 [RFC PATCH v2 0/4] Add initial device tree for MSM8916 A3U/A5U/L8150 Stephan Gerhold
2019-07-22 9:22 ` [RFC PATCH v2 1/4] dt-bindings: vendor-prefixes: Add Longcheer Technology Co., Ltd Stephan Gerhold
2019-07-22 15:12 ` Rob Herring [this message]
2019-07-22 9:22 ` [RFC PATCH v2 2/4] dt-bindings: qcom: Document bindings for new MSM8916 devices Stephan Gerhold
2019-07-22 15:12 ` Rob Herring
2019-07-22 9:22 ` [RFC PATCH v2 3/4] arm64: dts: qcom: Add device tree for Samsung Galaxy A3U/A5U Stephan Gerhold
2019-07-22 9:22 ` [RFC PATCH v2 4/4] arm64: dts: qcom: Add device tree for Longcheer L8150 Stephan Gerhold
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=CAL_Jsq+Fe+bExtqXRHNoEvATh3qVuDBnS0SqgSJenZs+yDVOOQ@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=stephan@gerhold.net \
/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).