public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	linux-iio@vger.kernel.org, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-kernel@vger.kernel.org,
	Bao Cheng Su <baocheng.su@siemens.com>,
	Chao Zeng <chao.zeng@siemens.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: vendor-prefixes: Add EVERLIGHT
Date: Tue, 13 Aug 2024 16:41:03 +0100	[thread overview]
Message-ID: <20240813-moaning-scrabble-48599c03b459@spud> (raw)
In-Reply-To: <1c79a109a7e91927a9380d2aee91fae32848d7f7.1723527641.git.jan.kiszka@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

On Tue, Aug 13, 2024 at 07:40:40AM +0200, Jan Kiszka wrote:
> From: Baocheng Su <baocheng.su@siemens.com>
> 
> Add vendor prefix for EVERLIGHT Electronics Co., Ltd.
> 
> Signed-off-by: Baocheng Su <baocheng.su@siemens.com>

This is missing your signoff Jan. With it,
Acked-by: Conor Dooley <conor.dooley@microchip.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 a70ce43b3dc0..1d2bf326fe91 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -486,6 +486,8 @@ patternProperties:
>      description: Eukréa Electromatique
>    "^everest,.*":
>      description: Everest Semiconductor Co. Ltd.
> +  "^everlight,.*":
> +    description: EVERLIGHT Electronics Co., Ltd.
>    "^everspin,.*":
>      description: Everspin Technologies, Inc.
>    "^evervision,.*":
> -- 
> 2.43.0
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-08-13 15:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13  5:40 [PATCH 0/3] iio: Add Everlight PM16D17 proximity sensor Jan Kiszka
2024-08-13  5:40 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add EVERLIGHT Jan Kiszka
2024-08-13 15:41   ` Conor Dooley [this message]
2024-08-13 15:46     ` Krzysztof Kozlowski
2024-08-13 15:53       ` Conor Dooley
2024-08-13  5:40 ` [PATCH 2/3] dt-bindings: iio: Add everlight pm16d17 binding Jan Kiszka
2024-08-13 15:52   ` Conor Dooley
2024-08-16  1:48     ` Li, Hua Qian
2024-08-16 16:11       ` Conor Dooley
2024-08-17 13:42       ` Jonathan Cameron
2024-08-26  7:12         ` Li, Hua Qian
2024-08-26  9:49           ` Jonathan Cameron
2024-08-14 19:10   ` Jonathan Cameron
2024-08-15  8:13     ` Jan Kiszka
2024-08-13  5:40 ` [PATCH 3/3] iio: proximity: Add support for everlight pmd16d17 sensor Jan Kiszka
2024-08-15  5:51   ` kernel test robot
2024-08-15 21:54   ` kernel test robot
2024-08-17 14:02   ` Jonathan Cameron

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=20240813-moaning-scrabble-48599c03b459@spud \
    --to=conor@kernel.org \
    --cc=baocheng.su@siemens.com \
    --cc=chao.zeng@siemens.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jan.kiszka@siemens.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.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