From: kernel test robot <lkp@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, Randy Dunlap <rdunlap@infradead.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] usb: typec: mux: select not-visible INTEL_SCU_IPC
Date: Sun, 30 Jan 2022 16:53:35 +0800 [thread overview]
Message-ID: <202201301532.7WyZkoRm-lkp@intel.com> (raw)
In-Reply-To: <20220130041220.9968-1-rdunlap@infradead.org>
Hi Randy,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on linux/master linus/master balbi-usb/testing/next peter-chen-usb/for-usb-next v5.17-rc1 next-20220128]
[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/Randy-Dunlap/usb-typec-mux-select-not-visible-INTEL_SCU_IPC/20220130-121346
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
config: ia64-allmodconfig (https://download.01.org/0day-ci/archive/20220130/202201301532.7WyZkoRm-lkp@intel.com/config)
compiler: ia64-linux-gcc (GCC) 11.2.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/15c19e705dc558a4a954897a8a4d369164035341
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Randy-Dunlap/usb-typec-mux-select-not-visible-INTEL_SCU_IPC/20220130-121346
git checkout 15c19e705dc558a4a954897a8a4d369164035341
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=ia64 SHELL=/bin/bash drivers/usb/typec/mux/
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/usb/typec/mux/intel_pmc_mux.c:19:10: fatal error: asm/intel_scu_ipc.h: No such file or directory
19 | #include <asm/intel_scu_ipc.h>
| ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for INTEL_SCU_IPC
Depends on X86 && X86_PLATFORM_DEVICES
Selected by
- TYPEC_MUX_INTEL_PMC && USB_SUPPORT && TYPEC && ACPI
vim +19 drivers/usb/typec/mux/intel_pmc_mux.c
6701adfa9693bd Heikki Krogerus 2020-03-02 18
b62851491a55bc Heikki Krogerus 2020-04-16 @19 #include <asm/intel_scu_ipc.h>
6701adfa9693bd Heikki Krogerus 2020-03-02 20
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
prev parent reply other threads:[~2022-01-30 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 4:12 [PATCH] usb: typec: mux: select not-visible INTEL_SCU_IPC Randy Dunlap
2022-01-30 8:53 ` 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=202201301532.7WyZkoRm-lkp@intel.com \
--to=lkp@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rdunlap@infradead.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