Re: [PATCH v5 1/4] dt-bindings: iio: light: veml6030: add veml6031x00 ALS series
"Javier Carrasco" <[email protected]>
| Newsgroups | org.kernel.vger.linux-iio,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Mon Aug 10, 2026 at 8:23 AM CEST, Krzysztof Kozlowski wrote: > On 07/08/2026 15:51, Javier Carrasco wrote: >> These ambient light sensors share their properties with the ones >> from the same manufacturer that are supported by this bindings. >> >> Note that only two datasheets are provided as every one of them covers >> two devices (veml6031x00/veml60311x00 and veml6031x01/veml60311x01). >> >> Reviewed-by: Krzysztof Kozlowski <[email protected]> >> Signed-off-by: Javier Carrasco <[email protected]> >> --- >> .../devicetree/bindings/iio/light/vishay,veml6030.yaml | 13 ++++++++++++- >> MAINTAINERS | 5 +++++ >> 2 files changed, 17 insertions(+), 1 deletion(-) >> >> diff --git a/Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml b/Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml >> index 0041e1db6838..6a387c76df35 100644 >> --- a/Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml >> +++ b/Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml >> @@ -4,7 +4,8 @@ >> $id: http://devicetree.org/schemas/iio/light/vishay,veml6030.yaml# >> $schema: http://devicetree.org/meta-schemas/core.yaml# >> >> -title: VEML3235, VEML3328, VEML6030, VEML6035 and VEML7700 Ambient Light Sensors (ALS) >> +title: VEML3235, VEML3328, VEML6030, VEML6031x00 series, VEML6035 >> +and VEML7700 Ambient Light Sensors (ALS) > > This was correct, now is broken. And was not even tested before sending... > > Best regards, > Krzysztof Yes, it is. I replied to the Sashiko email before this one arrived that a new device was added to the binding between versions and I just extended the title without further thinking. My bad, I have added the missing white spaces at the beginning of the second line for V6, validated the result, and included dt_binding_check in my CI pipeline to keep this from happening again. Thanks and best regards, Javier