mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Sebastien Bourdelin <sebastien.bourdelin@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
	himanshujha199640@gmail.com, mark.rutland@arm.com,
	robh+dt@kernel.org, pmeerw@pmeerw.net, lars@metafoo.de,
	knaack.h@gmx.de, jic23@kernel.org,
	Sebastien Bourdelin <sebastien.bourdelin@gmail.com>
Subject: Re: [PATCH 2/2] dt-bindings: iio: chemical: Add bindings for bme680
Date: Mon, 14 Jan 2019 12:01:57 +0800	[thread overview]
Message-ID: <201901141152.MwhU5vOB%fengguang.wu@intel.com> (raw)
In-Reply-To: <20190111193141.20607-2-sebastien.bourdelin@gmail.com>

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

Hi Sebastien,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on iio/togreg]
[also build test ERROR on v5.0-rc2 next-20190111]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Sebastien-Bourdelin/iio-chemical-bme680-Add-device-tree-support/20190114-063618
base:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

>> drivers/iio/chemical/bme680_i2c.c:77:1: error: Expected ; at end of declaration
>> drivers/iio/chemical/bme680_i2c.c:77:1: error: got extern
   In file included from include/linux/acpi.h:41:0,
                    from drivers/iio/chemical/bme680_i2c.c:14:
   include/linux/module.h:213:1: error: expected ',' or ';' before 'extern'
    extern typeof(name) __mod_##type##__##name##_device_table  \
    ^
   drivers/iio/chemical/bme680_i2c.c:77:1: note: in expansion of macro 'MODULE_DEVICE_TABLE'
    MODULE_DEVICE_TABLE(of, bme680_of_i2c_match);
    ^~~~~~~~~~~~~~~~~~~
--
>> drivers/iio/chemical/bme680_spi.c:117:1: error: Expected ; at end of declaration
>> drivers/iio/chemical/bme680_spi.c:117:1: error: got extern
>> drivers/iio/chemical/bme680_spi.c:123:43: error: undefined identifier 'of_match_ptr'
   In file included from include/linux/acpi.h:41:0,
                    from drivers/iio/chemical/bme680_spi.c:7:
   include/linux/module.h:213:1: error: expected ',' or ';' before 'extern'
    extern typeof(name) __mod_##type##__##name##_device_table  \
    ^
   drivers/iio/chemical/bme680_spi.c:117:1: note: in expansion of macro 'MODULE_DEVICE_TABLE'
    MODULE_DEVICE_TABLE(of, bme680_of_spi_match);
    ^~~~~~~~~~~~~~~~~~~
   drivers/iio/chemical/bme680_spi.c:123:22: error: implicit declaration of function 'of_match_ptr'; did you mean 'hash_ptr'? [-Werror=implicit-function-declaration]
      .of_match_table  = of_match_ptr(bme680_of_spi_match),
                         ^~~~~~~~~~~~
                         hash_ptr
   drivers/iio/chemical/bme680_spi.c:123:22: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
   drivers/iio/chemical/bme680_spi.c:123:22: note: (near initialization for 'bme680_spi_driver.driver.of_match_table')
   drivers/iio/chemical/bme680_spi.c:123:22: error: initializer element is not constant
   drivers/iio/chemical/bme680_spi.c:123:22: note: (near initialization for 'bme680_spi_driver.driver.of_match_table')
   cc1: some warnings being treated as errors

vim +77 drivers/iio/chemical/bme680_i2c.c

1b3bd859 Himanshu Jha        2018-07-26  72  
a8182f08 Sebastien Bourdelin 2019-01-11  73  static const struct of_device_id bme680_of_i2c_match[] = {
a8182f08 Sebastien Bourdelin 2019-01-11  74  	{ .compatible = "bosch,bme680", },
a8182f08 Sebastien Bourdelin 2019-01-11  75  	{},
a8182f08 Sebastien Bourdelin 2019-01-11  76  }
a8182f08 Sebastien Bourdelin 2019-01-11 @77  MODULE_DEVICE_TABLE(of, bme680_of_i2c_match);
a8182f08 Sebastien Bourdelin 2019-01-11  78  

:::::: The code at line 77 was first introduced by commit
:::::: a8182f084d7571c44c76305024da0f40a0911cf7 iio: chemical: bme680: Add device-tree support

:::::: TO: Sebastien Bourdelin <sebastien.bourdelin@gmail.com>
:::::: CC: 0day robot <lkp@intel.com>

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

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

  reply	other threads:[~2019-01-14  4:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11 19:31 [PATCH 1/2] iio: chemical: bme680: Add device-tree support Sebastien Bourdelin
2019-01-11 19:31 ` [PATCH 2/2] dt-bindings: iio: chemical: Add bindings for bme680 Sebastien Bourdelin
2019-01-14  4:01   ` kbuild test robot [this message]
2019-01-13 22:59 ` [PATCH 1/2] iio: chemical: bme680: Add device-tree support kbuild test robot
2019-01-13 22:59 ` kbuild test robot

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=201901141152.MwhU5vOB%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=himanshujha199640@gmail.com \
    --cc=jic23@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=sebastien.bourdelin@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

all inboxes | Powered by JetHome®