All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Ken Chen <chen.kenyy@inventec.com>
Cc: kbuild-all@01.org, linux@roeck-us.net, wsa@the-dreams.de,
	peda@axentia.se, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, Ken Chen <chen.kenyy@inventec.com>,
	joel@jms.id.au
Subject: Re: [PATCH linux dev-4.16] drivers: i2c: master arbiter: create driver
Date: Tue, 20 Mar 2018 15:00:07 +0800	[thread overview]
Message-ID: <201803201452.L9WBgx3Q%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180319113808.23485-1-chen.kenyy@inventec.com>

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

Hi Ken,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on v4.16-rc4]
[also build test ERROR on next-20180319]
[cannot apply to linux/master]
[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/Ken-Chen/drivers-i2c-master-arbiter-create-driver/20180320-134925
config: i386-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=i386 

All errors (new ones prefixed by >>):

>> drivers/i2c/muxes/i2c-mux-pca9641.c:23:10: fatal error: linux/i2c/pca954x.h: No such file or directory
    #include <linux/i2c/pca954x.h>
             ^~~~~~~~~~~~~~~~~~~~~
   compilation terminated.

vim +23 drivers/i2c/muxes/i2c-mux-pca9641.c

    22	
  > 23	#include <linux/i2c/pca954x.h>
    24	

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

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux@roeck-us.net, wsa@the-dreams.de,
	peda@axentia.se, linux-i2c@vger.kernel.org,
	linux-kernel@vger.kernel.org, Ken Chen <chen.kenyy@inventec.com>,
	joel@jms.id.au
Subject: Re: [PATCH linux dev-4.16] drivers: i2c: master arbiter: create driver
Date: Tue, 20 Mar 2018 15:00:07 +0800	[thread overview]
Message-ID: <201803201452.L9WBgx3Q%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180319113808.23485-1-chen.kenyy@inventec.com>

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

Hi Ken,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on v4.16-rc4]
[also build test ERROR on next-20180319]
[cannot apply to linux/master]
[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/Ken-Chen/drivers-i2c-master-arbiter-create-driver/20180320-134925
config: i386-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=i386 

All errors (new ones prefixed by >>):

>> drivers/i2c/muxes/i2c-mux-pca9641.c:23:10: fatal error: linux/i2c/pca954x.h: No such file or directory
    #include <linux/i2c/pca954x.h>
             ^~~~~~~~~~~~~~~~~~~~~
   compilation terminated.

vim +23 drivers/i2c/muxes/i2c-mux-pca9641.c

    22	
  > 23	#include <linux/i2c/pca954x.h>
    24	

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

  parent reply	other threads:[~2018-03-20  7:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 11:38 [PATCH linux dev-4.16] drivers: i2c: master arbiter: create driver Ken Chen
2018-03-19 11:38 ` Ken Chen
2018-03-19 12:45 ` Peter Rosin
2018-03-19 13:44   ` Guenter Roeck
2018-03-20  6:14     ` ChenKenYY 陳永營 TAO
2018-03-20  6:14       ` ChenKenYY 陳永營 TAO
2018-03-20  7:00 ` kbuild test robot [this message]
2018-03-20  7:00   ` 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=201803201452.L9WBgx3Q%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=chen.kenyy@inventec.com \
    --cc=joel@jms.id.au \
    --cc=kbuild-all@01.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=peda@axentia.se \
    --cc=wsa@the-dreams.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.