From: Conor Dooley <conor@kernel.org>
To: Artem Novak <artem122novak@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] dt-bindings: vendor-prefixes: Add Casio
Date: Thu, 12 Nov 2026 18:13:40 +0000 [thread overview]
Message-ID: <20261112-reprise-jukebox-41fb305e9044@spud> (raw)
In-Reply-To: <20261111212921.290857-1-artem122novak@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On Wed, Nov 11, 2026 at 03:29:21PM -0600, Artem Novak wrote:
> Add Casio Computer Co., Ltd. to the Devicetree vendor prefix
> registry.
>
> This prefix will be used by upcoming Devicetree bindings for
> Casio calculator hardware.
Why is this an RFC?
>
> Signed-off-by: Artem Novak <artem122novak@gmail.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 5471a06f93f1..f05475072eec 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -303,6 +303,8 @@ patternProperties:
> description: Capella Microsystems, Inc
> "^cascoda,.*":
> description: Cascoda, Ltd.
> + "^casio,.*":
> + description: Casio Computer Co., Ltd.
> "^catalyst,.*":
> description: Catalyst Semiconductor, Inc.
> "^cavium,.*":
> --
> 2.56.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-11-12 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 21:29 Artem Novak
2026-11-12 18:13 ` Conor Dooley [this message]
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=20261112-reprise-jukebox-41fb305e9044@spud \
--to=conor@kernel.org \
--cc=artem122novak@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®