From: Jonathan Cameron <jic23@kernel.org>
To: Crt Mori <cmo@melexis.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v3 0/2] iio: temperature: mlx90632: Add supply regulator
Date: Sun, 14 Aug 2022 15:21:35 +0100 [thread overview]
Message-ID: <20220814152135.6ac36cfb@jic23-huawei> (raw)
In-Reply-To: <20220808144804.1558849-1-cmo@melexis.com>
On Mon, 8 Aug 2022 16:48:04 +0200
Crt Mori <cmo@melexis.com> wrote:
> Add supply regulator to the sensor as initial update before proper power
> management is presented. This will reduce the diff for the following
> patches.
>
Hi Crt,
Series applied to what will be the togreg branch of iio.git after I've
rebased on rc1. Until then pushed out as testing for 0-day to see
if it can find anything we missed.
btw, your series are not coming through as threads which makes them (slightly)
harder to apply. For whatever reason the reply-to header field on
the emails isn't set.
Thanks,
Jonathan
> Changes in v3:
>
> - Style changes of few more arguments in one line
>
> Changes in v2:
>
> - Regulator voltage was removed as per comments from Jonathan Cameron
> and Lars-Peter Clausen
> - Style handling for the error reporting of the regulator DT binding
> was adjusted
> - NEW: Delay function was created and grouped together with call from
> the reset command, to ensure consistency and reduce the amount of
> code.
>
> Crt Mori (2):
> iio: temperature: mlx90632 Add supply regulator to sensor
> dt-bindings: iio: mlx90632 Add supply regulator documentation
>
> .../iio/temperature/melexis,mlx90632.yaml | 4 ++
> drivers/iio/temperature/mlx90632.c | 61 +++++++++++++++++--
> 2 files changed, 60 insertions(+), 5 deletions(-)
>
prev parent reply other threads:[~2022-08-14 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 14:48 [PATCH v3 0/2] iio: temperature: mlx90632: Add supply regulator Crt Mori
2022-08-14 14:21 ` 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=20220814152135.6ac36cfb@jic23-huawei \
--to=jic23@kernel.org \
--cc=cmo@melexis.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).