From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dharma.B@microchip.com
Cc: m.gonella.bolduc@gmail.com, jic23@kernel.org, lars@metafoo.de,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
Jonathan.Cameron@huawei.com, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: iio: light: fix missing type definition
Date: Thu, 6 Feb 2025 08:38:32 +0100 [thread overview]
Message-ID: <fc4c51e9-bd5a-4056-8e56-dd29ac0b4eca@kernel.org> (raw)
In-Reply-To: <1e1ff244-098b-4b3b-b430-8bed9ca8188c@microchip.com>
On 06/02/2025 03:41, Dharma.B@microchip.com wrote:
> On 05/02/25 5:07 pm, Krzysztof Kozlowski wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> On Wed, Feb 05, 2025 at 09:48:45AM +0530, Dharma Balasubiramani wrote:
>>> Add the missing type definition for ps-cancellation-current-picoamp property.
>>
>> It is not missing. You are using some older schema probably.
>
> Sorry, if I miss something here..
>
> There is no $Ref or type for ps-cancellation-current-picoamp property
There is a ref in dtschema.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/Documentation/devicetree/bindings/iio/light/brcm,apds9160.yaml#n39
>
> I checked in other bindings as well.
>
> I get the following warning while make dtbs_check or dt_binding_check
>
> Documentation/devicetree/bindings/iio/light/brcm,apds9160.yaml:
> ps-cancellation-current-picoamp: missing type definition
>
> Should I need to update anything?
As I said - older schema, so yes, you need to update your dtschema or
wait for new release.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-02-06 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 4:18 [PATCH] dt-bindings: iio: light: fix missing type definition Dharma Balasubiramani
2025-02-05 11:37 ` Krzysztof Kozlowski
2025-02-06 2:41 ` Dharma.B
2025-02-06 7:38 ` Krzysztof Kozlowski [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=fc4c51e9-bd5a-4056-8e56-dd29ac0b4eca@kernel.org \
--to=krzk@kernel.org \
--cc=Dharma.B@microchip.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=m.gonella.bolduc@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.