From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: cmo@melexis.com, jic23@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/3] iio: temperature: mlx90632 Add runtime powermanagement modes
Date: Mon, 3 Oct 2022 10:43:18 +0300 [thread overview]
Message-ID: <CAHp75VcbsE2Smwvpih--7OiMbw3DJeNYAma-prmDLwxqVodwrw@mail.gmail.com> (raw)
In-Reply-To: <e039d9bd-d2e7-a215-4ec2-7f760e1f83b1@wanadoo.fr>
On Sun, Oct 2, 2022 at 7:11 PM Christophe JAILLET
<christophe.jaillet@wanadoo.fr> wrote:
> Le 02/10/2022 à 18:09, Christophe JAILLET a écrit :
...
> >> static int mlx90632_read_raw(struct iio_dev *indio_dev,
> >> struct iio_chan_spec const *channel, int *val,
> >> int *val2, long mask)
> >> {
> >> struct mlx90632_data *data = iio_priv(indio_dev);
> >> int ret;
> >> + int cr;
> >
> > This 'cr' seems to be unused.
>
> Ok, used in patch 2/3.
> Sorry for the noise.
But it should be used in this patch if it was introduced by it.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-10-03 8:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 8:13 [PATCH v6 0/3] iio: temperature: mlx90632: Add powermanagement cmo
2022-09-22 8:13 ` [PATCH v6 1/3] iio: temperature: mlx90632 Add runtime powermanagement modes cmo
2022-10-02 16:09 ` Christophe JAILLET
2022-10-02 16:11 ` Christophe JAILLET
2022-10-02 16:11 ` Christophe JAILLET
2022-10-03 7:43 ` Andy Shevchenko [this message]
2022-10-03 8:20 ` Crt Mori
2022-10-09 16:36 ` Jonathan Cameron
2022-09-22 8:13 ` [PATCH v6 2/3] iio: temperature: mlx90632 Read sampling frequency cmo
2022-09-22 8:13 ` [PATCH v6 3/3] iio: temperature: mlx90632 Change return value of sensor measurement channel cmo
2022-09-24 16:32 ` [PATCH v6 0/3] iio: temperature: mlx90632: Add powermanagement Jonathan Cameron
2022-09-26 13:20 ` Crt Mori
2022-10-02 11:25 ` Jonathan Cameron
2022-10-02 14:36 ` Crt Mori
2022-10-02 14:43 ` Jonathan Cameron
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=CAHp75VcbsE2Smwvpih--7OiMbw3DJeNYAma-prmDLwxqVodwrw@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=cmo@melexis.com \
--cc=jic23@kernel.org \
--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).