linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Puranjay Mohan <puranjay12@gmail.com>,
	Michael.Hennerich@analog.com, alexandru.ardelean@analog.com,
	jic23@kernel.org, devicetree@vger.kernel.org,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	lars@metafoo.de, Dragos.Bogdan@analog.com,
	Darius.Berghe@analog.com
Cc: kbuild-all@lists.01.org, Puranjay Mohan <puranjay12@gmail.com>
Subject: Re: [PATCH v1 2/2] iio: accel: Add driver support for ADXL355
Date: Wed, 21 Jul 2021 22:11:49 +0800	[thread overview]
Message-ID: <202107212214.PEdvKUWS-lkp@intel.com> (raw)
In-Reply-To: <20210721095235.218519-3-puranjay12@gmail.com>

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

Hi Puranjay,

I love your patch! Yet something to improve:

[auto build test ERROR on iio/togreg]
[also build test ERROR on robh/for-next linus/master v5.14-rc2 next-20210721]
[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/Puranjay-Mohan/iio-accel-add-support-for-ADXL355/20210721-180632
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: m68k-allmodconfig (attached as .config)
compiler: m68k-linux-gcc (GCC) 10.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/1abb9f2f7fa2b5ed06f84a705806b1b907532bfa
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Puranjay-Mohan/iio-accel-add-support-for-ADXL355/20210721-180632
        git checkout 1abb9f2f7fa2b5ed06f84a705806b1b907532bfa
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross O=build_dir ARCH=m68k SHELL=/bin/bash drivers/iio/accel/

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

All errors (new ones prefixed by >>):

>> drivers/iio/accel/adxl355_core.c:19:34: error: static declaration of 'adxl355_read_reg_range' follows non-static declaration
      19 | static const struct regmap_range adxl355_read_reg_range[] = {
         |                                  ^~~~~~~~~~~~~~~~~~~~~~
   In file included from drivers/iio/accel/adxl355_core.c:17:
   drivers/iio/accel/adxl355.h:73:34: note: previous declaration of 'adxl355_read_reg_range' was here
      73 | extern const struct regmap_range adxl355_read_reg_range[];
         |                                  ^~~~~~~~~~~~~~~~~~~~~~
>> drivers/iio/accel/adxl355_core.c:30:34: error: static declaration of 'adxl355_write_reg_range' follows non-static declaration
      30 | static const struct regmap_range adxl355_write_reg_range[] = {
         |                                  ^~~~~~~~~~~~~~~~~~~~~~~
   In file included from drivers/iio/accel/adxl355_core.c:17:
   drivers/iio/accel/adxl355.h:77:34: note: previous declaration of 'adxl355_write_reg_range' was here
      77 | extern const struct regmap_range adxl355_write_reg_range[];
         |                                  ^~~~~~~~~~~~~~~~~~~~~~~


vim +/adxl355_read_reg_range +19 drivers/iio/accel/adxl355_core.c

    18	
  > 19	static const struct regmap_range adxl355_read_reg_range[] = {
    20		regmap_reg_range(ADXL355_DEVID_AD, ADXL355_FIFO_DATA),
    21		regmap_reg_range(ADXL355_OFFSET_X_H, ADXL355_SELF_TEST)
    22	};
    23	
    24	const struct regmap_access_table adxl355_readable_regs_tbl = {
    25		.yes_ranges = adxl355_read_reg_range,
    26		.n_yes_ranges = ARRAY_SIZE(adxl355_read_reg_range),
    27	};
    28	EXPORT_SYMBOL_GPL(adxl355_readable_regs_tbl);
    29	
  > 30	static const struct regmap_range adxl355_write_reg_range[] = {
    31		regmap_reg_range(ADXL355_OFFSET_X_H, ADXL355_RESET)
    32	};
    33	

---
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: 60750 bytes --]

      parent reply	other threads:[~2021-07-21 14:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21  9:52 [PATCH v1 0/2] iio: accel: add support for ADXL355 Puranjay Mohan
2021-07-21  9:52 ` [PATCH v1 1/2] dt-bindings: iio: accel: Add ADXL355 in trivial-devices Puranjay Mohan
2021-07-21  9:52 ` [PATCH v1 2/2] iio: accel: Add driver support for ADXL355 Puranjay Mohan
2021-07-21 10:46   ` Alexandru Ardelean
2021-07-21 11:40     ` Puranjay Mohan
2021-07-21 12:05       ` Alexandru Ardelean
2021-07-21 14:11   ` kernel test robot [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=202107212214.PEdvKUWS-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Darius.Berghe@analog.com \
    --cc=Dragos.Bogdan@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=alexandru.ardelean@analog.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=puranjay12@gmail.com \
    /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).