mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: alexandru.tachici@analog.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, jic23@kernel.org
Subject: Re: [PATCH v5 1/1] iio: adc: ad7124: allow more than 8 channels
Date: Thu, 11 Mar 2021 20:34:23 +0800	[thread overview]
Message-ID: <202103112049.H4pqjNYd-lkp@intel.com> (raw)
In-Reply-To: <20210311091154.47785-2-alexandru.tachici@analog.com>

[-- Attachment #1: Type: text/plain, Size: 2142 bytes --]

Hi,

I love your patch! Perhaps something to improve:

[auto build test WARNING on iio/togreg]
[also build test WARNING on linux/master linus/master v5.12-rc2 next-20210311]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/alexandru-tachici-analog-com/iio-adc-ad7124-allow-more-than-8-channels/20210311-170758
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: openrisc-randconfig-m031-20210311 (attached as .config)
compiler: or1k-linux-gcc (GCC) 9.3.0

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

smatch warnings:
drivers/iio/adc/ad7124.c:369 ad7124_init_config_vref() warn: inconsistent indenting

vim +369 drivers/iio/adc/ad7124.c

   356	
   357	static int ad7124_init_config_vref(struct ad7124_state *st, struct ad7124_channel_config *cfg)
   358	{
   359		unsigned int refsel = cfg->refsel;
   360	
   361		switch (refsel) {
   362		case AD7124_REFIN1:
   363		case AD7124_REFIN2:
   364		case AD7124_AVDD_REF:
   365			if (IS_ERR(st->vref[refsel])) {
   366				dev_err(&st->sd.spi->dev,
   367					"Error, trying to use external voltage reference without a %s regulator.\n",
   368					ad7124_ref_names[refsel]);
 > 369					return PTR_ERR(st->vref[refsel]);
   370			}
   371			cfg->vref_mv = regulator_get_voltage(st->vref[refsel]);
   372			/* Conversion from uV to mV */
   373			cfg->vref_mv /= 1000;
   374			return 0;
   375		case AD7124_INT_REF:
   376			cfg->vref_mv = 2500;
   377			st->adc_control &= ~AD7124_ADC_CTRL_REF_EN_MSK;
   378			st->adc_control |= AD7124_ADC_CTRL_REF_EN(1);
   379			return ad_sd_write_reg(&st->sd, AD7124_ADC_CONTROL,
   380					      2, st->adc_control);
   381		default:
   382			dev_err(&st->sd.spi->dev, "Invalid reference %d\n", refsel);
   383			return -EINVAL;
   384		}
   385	}
   386	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32298 bytes --]

  parent reply	other threads:[~2021-03-11 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-11  9:11 [PATCH v5 0/1] " alexandru.tachici
2021-03-11  9:11 ` [PATCH v5 1/1] " alexandru.tachici
2021-03-11 11:32   ` kernel test robot
2021-03-11 12:34   ` kernel test robot [this message]
2021-03-13 16:37   ` 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=202103112049.H4pqjNYd-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexandru.tachici@analog.com \
    --cc=jic23@kernel.org \
    --cc=kbuild-all@lists.01.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

all inboxes | Powered by JetHome®