From: Daniel Scally <dan.scally@ideasonboard.com>
To: krzysztof.kozlowski@linaro.org, shawnguo@kernel.org,
robh@kernel.org, marcel.ziswiler@toradex.com, leoyang.li@nxp.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
laurent.pinchart@ideasonboard.com,
kieran.bingham@ideasonboard.com, debix-tech@polyhex.net,
Daniel Scally <dan.scally@ideasonboard.com>
Subject: [PATCH v4 1/3] dt-bindings: vendor-prefixes: Add Polyhex Technology Co.
Date: Mon, 17 Oct 2022 16:10:48 +0100 [thread overview]
Message-ID: <20221017151050.2321919-2-dan.scally@ideasonboard.com> (raw)
In-Reply-To: <20221017151050.2321919-1-dan.scally@ideasonboard.com>
Add an entry for Polyhex Technology Co. to vendor-prefixes.yaml
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Tested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Daniel Scally <dan.scally@ideasonboard.com>
---
Changes in v4:
- None
Changes in v3:
- None
Changes in v2:
- None
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 2f0151e9f6be..7ba1d2c11aa9 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -995,6 +995,8 @@ patternProperties:
description: PocketBook International SA
"^polaroid,.*":
description: Polaroid Corporation
+ "^polyhex,.*":
+ description: Polyhex Technology Co. Ltd.
"^portwell,.*":
description: Portwell Inc.
"^poslab,.*":
--
2.34.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Scally <dan.scally@ideasonboard.com>
To: krzysztof.kozlowski@linaro.org, shawnguo@kernel.org,
robh@kernel.org, marcel.ziswiler@toradex.com, leoyang.li@nxp.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
laurent.pinchart@ideasonboard.com,
kieran.bingham@ideasonboard.com, debix-tech@polyhex.net,
Daniel Scally <dan.scally@ideasonboard.com>
Subject: [PATCH v4 1/3] dt-bindings: vendor-prefixes: Add Polyhex Technology Co.
Date: Mon, 17 Oct 2022 16:10:48 +0100 [thread overview]
Message-ID: <20221017151050.2321919-2-dan.scally@ideasonboard.com> (raw)
In-Reply-To: <20221017151050.2321919-1-dan.scally@ideasonboard.com>
Add an entry for Polyhex Technology Co. to vendor-prefixes.yaml
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Reviewed-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
Tested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Daniel Scally <dan.scally@ideasonboard.com>
---
Changes in v4:
- None
Changes in v3:
- None
Changes in v2:
- None
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 2f0151e9f6be..7ba1d2c11aa9 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -995,6 +995,8 @@ patternProperties:
description: PocketBook International SA
"^polaroid,.*":
description: Polaroid Corporation
+ "^polyhex,.*":
+ description: Polyhex Technology Co. Ltd.
"^portwell,.*":
description: Portwell Inc.
"^poslab,.*":
--
2.34.1
next prev parent reply other threads:[~2022-10-17 15:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 15:10 [PATCH v4 0/3] Debix Model A board devicetree Daniel Scally
2022-10-17 15:10 ` Daniel Scally
2022-10-17 15:10 ` Daniel Scally [this message]
2022-10-17 15:10 ` [PATCH v4 1/3] dt-bindings: vendor-prefixes: Add Polyhex Technology Co Daniel Scally
2022-10-17 15:10 ` [PATCH v4 2/3] dt-bindings: arm: fsl: Enumerate Debix Model A Board Daniel Scally
2022-10-17 15:10 ` Daniel Scally
2022-10-17 15:10 ` [PATCH v4 3/3] arm64: dts: Add device tree for the " Daniel Scally
2022-10-17 15:10 ` Daniel Scally
2022-10-29 3:50 ` Shawn Guo
2022-10-29 3:50 ` Shawn Guo
2022-12-06 8:05 ` Dan Scally
2022-12-06 8:05 ` Dan Scally
2022-12-01 17:10 ` Ahmad Fatoum
2022-12-01 17:10 ` Ahmad Fatoum
2022-12-01 21:22 ` Kieran Bingham
2022-12-01 21:22 ` Kieran Bingham
2022-12-06 10:25 ` Dan Scally
2022-12-06 10:25 ` Dan Scally
2022-12-06 10:45 ` Laurent Pinchart
2022-12-06 10:45 ` Laurent Pinchart
2022-12-06 10:52 ` Ahmad Fatoum
2022-12-06 10:52 ` Ahmad Fatoum
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=20221017151050.2321919-2-dan.scally@ideasonboard.com \
--to=dan.scally@ideasonboard.com \
--cc=debix-tech@polyhex.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marcel.ziswiler@toradex.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.