From: Liviu Dudau <liviu.dudau@arm.com>
To: Cunyuan Liu <cunyuan.liu@cixtech.com>
Cc: maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
neil.armstrong@linaro.org, heiko@sntech.de, marex@nabladev.com,
dev@kael-k.io, prabhakar.mahadev-lad.rj@bp.renesas.com,
andre.przywara@arm.com, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
cix-kernel-upstream@cixtech.com
Subject: Re: [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add Arm Technology (China) Co., Ltd.
Date: Thu, 19 Mar 2026 16:32:05 +0000 [thread overview]
Message-ID: <abwlBZ0nORcTOUby@e142607> (raw)
In-Reply-To: <20260313033119.33686-2-cunyuan.liu@cixtech.com>
On Fri, Mar 13, 2026 at 11:31:17AM +0800, Cunyuan Liu wrote:
> Add "armchina" vendor prefix for Arm Technology (China) Co., Ltd.
>
> Link: https://www.armchina.com/
>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Cunyuan Liu <cunyuan.liu@cixtech.com>
Reviewed-by: Liviu Dudau <liviu.dudau@arm.com>
Rob, should I take the whole series through drm-misc-next or should I split the bindings
into a separate pull?
Best regards,
Liviu
> ---
> 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 ee7fd3cfe203..c7ca7f43925b 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -172,6 +172,8 @@ patternProperties:
> description: ARM Ltd.
> "^armadeus,.*":
> description: ARMadeus Systems SARL
> + "^armchina,.*":
> + description: Arm Technology (China) Co., Ltd.
> "^armsom,.*":
> description: ArmSoM Technology Co., Ltd.
> "^arrow,.*":
> --
> 2.53.0
>
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
next prev parent reply other threads:[~2026-03-19 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 3:31 [PATCH v2 0/3] Arm China Linlon-D6 display controller support Cunyuan Liu
2026-03-13 3:31 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add Arm Technology (China) Co., Ltd Cunyuan Liu
2026-03-19 16:32 ` Liviu Dudau [this message]
2026-03-13 3:31 ` [PATCH v2 2/3] dt-bindings: display: arm,komeda: add Arm China Linlon D6 compatible Cunyuan Liu
2026-03-21 20:23 ` Krzysztof Kozlowski
2026-03-13 3:31 ` [PATCH v2 3/3] drm/komeda: Add support for Arm China Linlon-D6 Cunyuan Liu
2026-03-24 16:10 ` [PATCH v2 0/3] Arm China Linlon-D6 display controller support Liviu Dudau
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=abwlBZ0nORcTOUby@e142607 \
--to=liviu.dudau@arm.com \
--cc=airlied@gmail.com \
--cc=andre.przywara@arm.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=cunyuan.liu@cixtech.com \
--cc=dev@kael-k.io \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@nabladev.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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