From: kbuild test robot <lkp@intel.com>
To: Prashant Malani <pmalani@chromium.org>
Cc: kbuild-all@lists.01.org, enric.balletbo@collabora.com,
groeck@chromium.org, bleung@chromium.org, lee.jones@linaro.org,
linux-kernel@vger.kernel.org, Jon Flatley <jflat@chromium.org>,
Prashant Malani <pmalani@chromium.org>
Subject: Re: [PATCH v2] platform: chrome: Add cros-ec-pd-notify driver
Date: Sun, 22 Dec 2019 09:27:34 +0800 [thread overview]
Message-ID: <201912220950.anXPZueT%lkp@intel.com> (raw)
In-Reply-To: <20191218230701.59166-1-pmalani@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
Hi Prashant,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on chrome-platform-linux/for-next]
[cannot apply to ljones-mfd/for-mfd-next linus/master v5.5-rc2 next-20191220]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Prashant-Malani/platform-chrome-Add-cros-ec-pd-notify-driver/20191222-065317
base: https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.5.0-3) 7.5.0
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/platform/chrome/cros_ec_pd_notify.c:10:10: fatal error: linux/mfd/cros_ec.h: No such file or directory
#include <linux/mfd/cros_ec.h>
^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +10 drivers/platform/chrome/cros_ec_pd_notify.c
> 10 #include <linux/mfd/cros_ec.h>
11 #include <linux/platform_data/cros_ec_commands.h>
12 #include <linux/platform_data/cros_ec_pd_notify.h>
13 #include <linux/platform_data/cros_ec_proto.h>
14 #include <linux/platform_device.h>
15
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 70427 bytes --]
prev parent reply other threads:[~2019-12-22 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 23:07 [PATCH v2] platform: chrome: Add cros-ec-pd-notify driver Prashant Malani
2019-12-19 9:44 ` Enric Balletbo i Serra
2019-12-19 20:10 ` Prashant Malani
2019-12-22 1:27 ` kbuild 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=201912220950.anXPZueT%lkp@intel.com \
--to=lkp@intel.com \
--cc=bleung@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=jflat@chromium.org \
--cc=kbuild-all@lists.01.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.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