From: <Dharma.B@microchip.com>
To: <krzk@kernel.org>
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 02:41:04 +0000 [thread overview]
Message-ID: <1e1ff244-098b-4b3b-b430-8bed9ca8188c@microchip.com> (raw)
In-Reply-To: <20250205-enormous-wise-copperhead-c1c0a9@krzk-bin>
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
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?
>
> Best regards,
> Krzysztof
>
--
With Best Regards,
Dharma B.
next prev parent reply other threads:[~2025-02-06 2:41 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 [this message]
2025-02-06 7:38 ` Krzysztof Kozlowski
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=1e1ff244-098b-4b3b-b430-8bed9ca8188c@microchip.com \
--to=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=krzk@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox