On Tue, 6 Apr 2021 09:32:44 +0100
Jonathan Cameron <jic23@xxxxxxxxxx> wrote:
> From: Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx>
>
> This doesn't appear to generate a warning on all versions of GCC, but
> 0-day reported it and the report looks valid.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx>
> Reported-by: kbuild test robot <lkp@xxxxxxxxx>
For this one, it's the sort of thing I'd normally just roll into the original
patch, but there is a merge in my tree after this, so in the interests of
simplicity I've applied it on top.
Applied to the togreg branch of iio.git and pushed out as testing for the
autobuilders to take another look at it and see what I got wrong this time :)
Jonathan
> ---
> drivers/iio/cdc/ad7150.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/cdc/ad7150.c b/drivers/iio/cdc/ad7150.c
> index f9cce1a64586..ebe112b4618b 100644
> --- a/drivers/iio/cdc/ad7150.c
> +++ b/drivers/iio/cdc/ad7150.c
> @@ -235,7 +235,7 @@ static int ad7150_write_event_config(struct iio_dev *indio_dev,
> enum iio_event_direction dir, int state)
> {
> struct ad7150_chip_info *chip = iio_priv(indio_dev);
> - int ret;
> + int ret = 0;
>
> /*
> * There is only a single shared control and no on chip
