From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Rishi Gupta <gupt21@gmail.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: [PATCH 1/7] dt-bindings: iio: light: veml6030: rename to add manufacturer
Date: Fri, 13 Sep 2024 15:18:56 +0200 [thread overview]
Message-ID: <20240913-veml6035-v1-1-0b09c0c90418@gmail.com> (raw)
In-Reply-To: <20240913-veml6035-v1-0-0b09c0c90418@gmail.com>
Follow the common pattern manufacturer,devicename.
Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
---
.../bindings/iio/light/{veml6030.yaml => vishay,veml6030.yaml} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/iio/light/veml6030.yaml b/Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml
similarity index 95%
rename from Documentation/devicetree/bindings/iio/light/veml6030.yaml
rename to Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml
index fb19a2d7a849..7f4995557570 100644
--- a/Documentation/devicetree/bindings/iio/light/veml6030.yaml
+++ b/Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0+
%YAML 1.2
---
-$id: http://devicetree.org/schemas/iio/light/veml6030.yaml#
+$id: http://devicetree.org/schemas/iio/light/vishay,veml6030.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: VEML6030 Ambient Light Sensor (ALS)
--
2.43.0
next prev parent reply other threads:[~2024-09-13 13:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 13:18 [PATCH 0/7] iio: light: veml6030: fix issues and add support for veml6035 Javier Carrasco
2024-09-13 13:18 ` Javier Carrasco [this message]
2024-09-13 16:53 ` [PATCH 1/7] dt-bindings: iio: light: veml6030: rename to add manufacturer Conor Dooley
2024-09-14 14:52 ` Jonathan Cameron
2024-09-13 13:18 ` [PATCH 2/7] dt-bindings: iio: light: veml6030: add veml6035 Javier Carrasco
2024-09-13 16:55 ` Conor Dooley
2024-09-13 13:18 ` [PATCH 3/7] iio: light: veml6030: fix IIO device retrieval from embedded device Javier Carrasco
2024-09-14 14:51 ` Jonathan Cameron
2024-09-13 13:18 ` [PATCH 4/7] iio: light: veml6030: make use of regmap_set_bits() Javier Carrasco
2024-09-14 14:54 ` Jonathan Cameron
2024-09-13 13:19 ` [PATCH 5/7] iio: light: veml6030: update sensor resolution Javier Carrasco
2024-09-14 14:57 ` Jonathan Cameron
2024-09-15 8:31 ` Javier Carrasco
2024-09-28 14:38 ` Jonathan Cameron
2024-09-13 13:19 ` [PATCH 6/7] iio: light: veml6030: add set up delay after any power on sequence Javier Carrasco
2024-09-14 14:59 ` Jonathan Cameron
2024-09-13 13:19 ` [PATCH 7/7] iio: light: veml6030: add support for veml6035 Javier Carrasco
2024-09-14 16:03 ` Jonathan Cameron
2024-09-16 6:19 ` Javier Carrasco
2024-09-28 14:40 ` 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=20240913-veml6035-v1-1-0b09c0c90418@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gupt21@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--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;
as well as URLs for NNTP newsgroup(s).