From: Jonathan Cameron <jic23@kernel.org>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 0/7] iio: light: veml6070: update code to current IIO best practices
Date: Mon, 30 Sep 2024 10:00:22 +0100 [thread overview]
Message-ID: <20240930100022.1c9bfe2e@jic23-huawei> (raw)
In-Reply-To: <20240929-veml6070-cleanup-v1-0-a9350341a646@gmail.com>
On Sun, 29 Sep 2024 22:38:45 +0200
Javier Carrasco <javier.carrasco.cruz@gmail.com> wrote:
> This series updates the driver in preparation to add new features. The
> cleanup consists of:
>
> 1. Device-managed registering for:
> - iio device
> - action (unregister i2c device)
> - regulator
>
> 2. Code update to use a guard for the mutex handling and
> dev_err_probe in the probe function.
>
> 3. Devicetree support (document the device bindings and register the
> compatible in the driver).
>
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Nice. Applied to the togreg branch of iio.git and pushed out as testing.
thanks,
Jonathan
> ---
> Javier Carrasco (7):
> iio: light: veml6070: add action for i2c_unregister_device
> iio: light: veml6070: use guard to handle mutex
> iio: light: veml6070: use device managed iio_device_register
> iio: light: veml6070: add support for a regulator
> dt-bindings: iio: light: vishay,veml6075: add vishay,veml6070
> iio: light: veml6070: add devicetree support
> iio: light: veml6070: use dev_err_probe in probe function
>
> .../bindings/iio/light/vishay,veml6075.yaml | 3 +-
> drivers/iio/light/veml6070.c | 63 +++++++++++-----------
> 2 files changed, 35 insertions(+), 31 deletions(-)
> ---
> base-commit: 4057951fb272efda718dca665f6607c348d5785b
> change-id: 20240929-veml6070-cleanup-70b609bb1f0f
>
> Best regards,
prev parent reply other threads:[~2024-09-30 9:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 20:38 [PATCH 0/7] iio: light: veml6070: update code to current IIO best practices Javier Carrasco
2024-09-29 20:38 ` [PATCH 1/7] iio: light: veml6070: add action for i2c_unregister_device Javier Carrasco
2024-09-29 20:38 ` [PATCH 2/7] iio: light: veml6070: use guard to handle mutex Javier Carrasco
2024-09-29 20:38 ` [PATCH 3/7] iio: light: veml6070: use device managed iio_device_register Javier Carrasco
2024-09-29 20:38 ` [PATCH 4/7] iio: light: veml6070: add support for a regulator Javier Carrasco
2024-09-29 20:38 ` [PATCH 5/7] dt-bindings: iio: light: vishay,veml6075: add vishay,veml6070 Javier Carrasco
2024-09-30 7:01 ` Krzysztof Kozlowski
2024-09-29 20:38 ` [PATCH 6/7] iio: light: veml6070: add devicetree support Javier Carrasco
2024-09-30 9:00 ` Jonathan Cameron
2024-09-29 20:38 ` [PATCH 7/7] iio: light: veml6070: use dev_err_probe in probe function Javier Carrasco
2024-09-30 9:00 ` Jonathan Cameron [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=20240930100022.1c9bfe2e@jic23-huawei \
--to=jic23@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=javier.carrasco.cruz@gmail.com \
--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