From: Benjamin Fair <benjaminfair@google.com>
To: Joel Stanley <joel@jms.id.au>
Cc: devicetree@vger.kernel.org,
Mohaimen alsmarai <Mohaimen.alsamarai@fii-na.com>,
Mustatfa Shehabi <Mustafa.Shehabi@fii-na.com>,
Rob Herring <robh+dt@kernel.org>,
Lancelot Kao <lancelot.kao@fii-usa.com>,
linux-arm-kernel@lists.infradead.org,
Vivekanand Veeracholan <vveerach@google.com>
Subject: Re: [PATCH] dt-bindings: vendor-prefixes: Add FII
Date: Thu, 19 Nov 2020 10:28:40 -0800 [thread overview]
Message-ID: <CADKL2t5FWfg+j997WFD5TO6vG9nrpH3FpLoW1XvPbtrP_ttR8g@mail.gmail.com> (raw)
In-Reply-To: <20201119073230.123888-1-joel@jms.id.au>
On Wed, 18 Nov 2020 at 23:32, Joel Stanley <joel@jms.id.au> wrote:
>
> Adds Foxconn Industrial Internet, who have submitted a BMC device tree.
>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
Reviewed-by: Benjamin Fair <benjaminfair@google.com>
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index 2735be1a8470..a64e03e39e9c 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -377,6 +377,8 @@ patternProperties:
> description: Shenzhen Feixin Photoelectic Co., Ltd
> "^feiyang,.*":
> description: Shenzhen Fly Young Technology Co.,LTD.
> + "^fii,.*":
> + description: Foxconn Industrial Internet
> "^firefly,.*"
> description: Firefly
> "^focaltech,.*":
> --
> 2.29.2
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-11-19 18:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 7:32 [PATCH] dt-bindings: vendor-prefixes: Add FII Joel Stanley
2020-11-19 18:28 ` Benjamin Fair [this message]
2020-12-07 22:02 ` Rob Herring
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=CADKL2t5FWfg+j997WFD5TO6vG9nrpH3FpLoW1XvPbtrP_ttR8g@mail.gmail.com \
--to=benjaminfair@google.com \
--cc=Mohaimen.alsamarai@fii-na.com \
--cc=Mustafa.Shehabi@fii-na.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=lancelot.kao@fii-usa.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=vveerach@google.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).