From: Rob Herring <robh@kernel.org>
To: Shreeya Patel <shreeya.patel@collabora.com>
Cc: dmitry.osipenko@collabora.com, devicetree@vger.kernel.org,
kernel@collabora.com, robh+dt@kernel.org, jic23@kernel.org,
alvaro.soliverez@collabora.com, andy.shevchenko@gmail.com,
lars@metafoo.de, Zhigang.Shi@liteon.com, krisman@collabora.com,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH v9 1/2] dt-bindings: Document ltrf216a light sensor bindings
Date: Wed, 20 Jul 2022 15:40:28 -0600 [thread overview]
Message-ID: <20220720214028.GA4029656-robh@kernel.org> (raw)
In-Reply-To: <20220715111626.1066513-2-shreeya.patel@collabora.com>
On Fri, 15 Jul 2022 16:46:25 +0530, Shreeya Patel wrote:
> Add devicetree bindings for ltrf216a ambient light sensor.
>
> Signed-off-by: Shreeya Patel <shreeya.patel@collabora.com>
> ---
>
> Changes in v7
> - Fix the error reported by kernel test robot.
>
> Changes in v5
> - Remove deprecated string 'ltr' from the bindings.
>
> Changes in v3
> - Fix indentation in the example section
>
> Changes in v2
> - Take over the maintainership for the bindings
> - Add interrupt and power supply property in DT bindings
>
> .../bindings/iio/light/liteon,ltrf216a.yaml | 49 +++++++++++++++++++
> 1 file changed, 49 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/light/liteon,ltrf216a.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-07-20 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 11:16 [PATCH v9 0/2] Add LTRF216A Driver Shreeya Patel
2022-07-15 11:16 ` [PATCH v9 1/2] dt-bindings: Document ltrf216a light sensor bindings Shreeya Patel
2022-07-20 21:40 ` Rob Herring [this message]
2022-07-15 11:16 ` [PATCH v9 2/2] iio: light: Add support for ltrf216a sensor Shreeya Patel
2022-07-16 22:29 ` kernel test robot
2022-07-18 17:25 ` Jonathan Cameron
2022-07-19 11:56 ` Dmitry Osipenko
2022-07-19 12:19 ` Jonathan Cameron
2022-07-19 13:11 ` Dmitry Osipenko
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=20220720214028.GA4029656-robh@kernel.org \
--to=robh@kernel.org \
--cc=Zhigang.Shi@liteon.com \
--cc=alvaro.soliverez@collabora.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.osipenko@collabora.com \
--cc=jic23@kernel.org \
--cc=kernel@collabora.com \
--cc=krisman@collabora.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shreeya.patel@collabora.com \
/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.