public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: Alexandru Ardelean <aardelean@baylibre.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, krzk+dt@kernel.org, robh@kernel.org,
	lars@metafoo.de, michael.hennerich@analog.com,
	gstols@baylibre.com
Subject: Re: [PATCH v7 8/8] iio: adc: ad7606: add support for AD7606C-{16,18} parts
Date: Tue, 1 Oct 2024 19:41:14 +0100	[thread overview]
Message-ID: <20241001194114.16e0ffa5@jic23-huawei> (raw)
In-Reply-To: <047034ae-135b-4ce9-a407-9b2a00841324@baylibre.com>

On Tue, 1 Oct 2024 08:42:23 -0500
David Lechner <dlechner@baylibre.com> wrote:

> On 10/1/24 3:26 AM, Alexandru Ardelean wrote:
> > On Thu, Sep 19, 2024 at 4:05 PM Alexandru Ardelean
> > <aardelean@baylibre.com> wrote:  
> >>  
> 
> ...
> 
> >> @@ -153,7 +349,19 @@ static int ad7606_scan_direct(struct iio_dev *indio_dev, unsigned int ch,
> >>         if (ret)
> >>                 goto error_ret;
> >>
> >> -       *val = sign_extend32(st->data[ch], 15);
> >> +       chan = &indio_dev->channels[ch + 1];
> >> +       if (chan->scan_type.sign == 'u') {
> >> +               if (storagebits > 16)
> >> +                       *val = st->data.buf32[ch];
> >> +               else
> >> +                       *val = st->data.buf16[ch];
> >> +               return 0;  
> > 
> > Arrggh...
> > I messed up here.
> > Guillaume found a bug here, where this should be "goto error_ret" or
> > do an "if ()  {} else {}"
> > How should we do it here?
if / else. Goto an error label when it's not an error would be horrible!
> > 
> > Do we send a fix-patch or send a new series?
> >   
> 
> Since this patch is already applied, just follow up with another
> patch with a Fixes: tag.

I sometimes tweak these sort of things if I haven't pushed out
as togreg yet (or they are really bad!) but in this case I'm not
100% sure what the comment is, so I'll just apply a fix on top.

So David is entirely correct in general but by luck of timing
this time I'll tweak it.

Please check the result in iio.git/testing
I'll hold off pushing that out as togreg until at least end of
tomorrow.  One more day o

Jonathan


> 
> 
> 


  reply	other threads:[~2024-10-01 18:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 13:04 [PATCH v7 0/8] iio: adc: ad7606: add support for AD7606C-{16,18} parts Alexandru Ardelean
2024-09-19 13:04 ` [PATCH v7 1/8] iio: adc: ad7606: add 'bits' parameter to channels macros Alexandru Ardelean
2024-09-23 14:50   ` David Lechner
2024-09-24  8:11     ` Alexandru Ardelean
2024-09-28 14:43       ` Jonathan Cameron
2024-09-19 13:04 ` [PATCH v7 2/8] iio: adc: ad7606: move 'val' pointer to ad7606_scan_direct() Alexandru Ardelean
2024-09-19 13:04 ` [PATCH v7 3/8] iio: adc: ad7606: move scale_setup as function pointer on chip-info Alexandru Ardelean
2024-09-19 13:04 ` [PATCH v7 4/8] iio: adc: ad7606: wrap channel ranges & scales into struct Alexandru Ardelean
2024-09-19 13:04 ` [PATCH v7 5/8] iio: adc: ad7606: rework available attributes for SW channels Alexandru Ardelean
2024-10-17 17:50   ` Jonathan Cameron
2024-10-19 16:15     ` Alexandru Ardelean
2024-09-19 13:04 ` [PATCH v7 6/8] dt-bindings: iio: adc: document diff-channels corner case for some ADCs Alexandru Ardelean
2024-09-19 13:04 ` [PATCH v7 7/8] dt-bindings: iio: adc: add docs for AD7606C-{16,18} parts Alexandru Ardelean
2024-09-19 13:04 ` [PATCH v7 8/8] iio: adc: ad7606: add support " Alexandru Ardelean
2024-10-01  8:26   ` Alexandru Ardelean
2024-10-01  9:26     ` Guillaume Stols
2024-10-01 13:42     ` David Lechner
2024-10-01 18:41       ` Jonathan Cameron [this message]
2024-10-02  6:12         ` Alexandru Ardelean
2024-10-04 13:54           ` Jonathan Cameron
2024-10-06 10:56             ` Jonathan Cameron
2024-10-07  7:00               ` Alexandru Ardelean

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=20241001194114.16e0ffa5@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=aardelean@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=gstols@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --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