devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Saravanan Sekar <sravanhome@gmail.com>
Cc: Sebastian Reichel <sre@kernel.org>,
	Lee Jones <lee.jones@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Linux PM <linux-pm@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	linux-iio <linux-iio@vger.kernel.org>
Subject: Re: [PATCH v2 1/6] iio: adc: mp2629: fix wrong comparison of channel
Date: Wed, 15 Jun 2022 11:53:04 +0200	[thread overview]
Message-ID: <CAHp75VdY4UUw9xSCFscSZrmd0s63LhcTSP16_Nn135iv2QSheQ@mail.gmail.com> (raw)
In-Reply-To: <20220614194225.2226447-1-sravanhome@gmail.com>

On Tue, Jun 14, 2022 at 9:42 PM Saravanan Sekar <sravanhome@gmail.com> wrote:
>
> Input voltage channel enum is compared against iio address instead
> of channel.

the channel

...

I do not see a cover letter, but FWIW,
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
for all patches except DT binding
Note, some of the comments regarding spelling were given, I believe
you are going to address them in v3.

> Fixes: 7abd9fb64682 ("iio: adc: mp2629: Add support for mp2629 ADC driver")
> Signed-off-by: Saravanan Sekar <sravanhome@gmail.com>
> ---
>  drivers/iio/adc/mp2629_adc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/mp2629_adc.c b/drivers/iio/adc/mp2629_adc.c
> index aca084f1e78a..e7fbfe92e884 100644
> --- a/drivers/iio/adc/mp2629_adc.c
> +++ b/drivers/iio/adc/mp2629_adc.c
> @@ -73,7 +73,7 @@ static int mp2629_read_raw(struct iio_dev *indio_dev,
>                 if (ret)
>                         return ret;
>
> -               if (chan->address == MP2629_INPUT_VOLT)
> +               if (chan->channel == MP2629_INPUT_VOLT)
>                         rval &= GENMASK(6, 0);
>                 *val = rval;
>                 return IIO_VAL_INT;
> --
> 2.25.1
>


-- 
With Best Regards,
Andy Shevchenko

      parent reply	other threads:[~2022-06-15  9:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 19:42 [PATCH v2 1/6] iio: adc: mp2629: fix wrong comparison of channel Saravanan Sekar
2022-06-14 19:42 ` [PATCH v2 2/6] dt-bindings: mfd: Add mp2733 compatible Saravanan Sekar
2022-06-14 20:48   ` Krzysztof Kozlowski
2022-06-15  1:28   ` Rob Herring
2022-06-14 19:42 ` [PATCH v2 3/6] mfd: mp2629: Add support for mps mp2733 battery charger Saravanan Sekar
2022-06-15  9:47   ` Andy Shevchenko
2022-06-14 19:42 ` [PATCH v2 4/6] iio: adc: mp2629: restrict input voltage mask for mp2629 Saravanan Sekar
2022-06-15  9:48   ` Andy Shevchenko
2022-06-14 19:42 ` [PATCH v2 5/6] power: supply: Add support for mp2733 battery charger Saravanan Sekar
2022-06-14 19:42 ` [PATCH v2 6/6] power: supply: mp2629: Add usb fast charge settings Saravanan Sekar
2022-06-15  9:51   ` Andy Shevchenko
2022-06-15  9:53 ` Andy Shevchenko [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=CAHp75VdY4UUw9xSCFscSZrmd0s63LhcTSP16_Nn135iv2QSheQ@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sravanhome@gmail.com \
    --cc=sre@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).