From: kbuild test robot <lkp@intel.com>
To: Amit K Bag <amit.k.bag@intel.com>, linux-firmware@kernel.org
Cc: Amit K Bag <amit.k.bag@intel.com>
Subject: Re: [PATCH 2/2] Bluetooth: btusb: Add support for TLV read version format and multiple Secure Boot Engines
Date: Wed, 22 Apr 2020 05:42:52 +0800 [thread overview]
Message-ID: <202004220502.bdsBRSzX%lkp@intel.com> (raw)
In-Reply-To: <20200417095012.8443-2-amit.k.bag@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
Hi Amit,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bluetooth-next/master]
[also build test ERROR on next-20200421]
[cannot apply to v5.7-rc2]
[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/Amit-K-Bag/Bluetooth-btusb-Add-support-for-Intel-Bluetooth-Device-Typhoon-Peak-8087-0032/20200420-144624
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
config: xtensa-randconfig-a001-20200421 (attached as .config)
compiler: xtensa-linux-gcc (GCC) 9.3.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day GCC_VERSION=9.3.0 make.cross ARCH=xtensa
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> xtensa-linux-ld: drivers/bluetooth/hci_ldisc.o:(.init.literal+0x58): undefined reference to `ag6xx_init'
xtensa-linux-ld: drivers/bluetooth/hci_ldisc.o: in function `hci_uart_init':
drivers/bluetooth/hci_ldisc.c:875: undefined reference to `ag6xx_init'
---
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: 33035 bytes --]
next prev parent reply other threads:[~2020-04-21 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 9:50 [PATCH 1/2] Bluetooth: btusb: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032) Amit K Bag
2020-04-17 9:50 ` Amit K Bag
2020-04-17 9:50 ` [PATCH 2/2] Bluetooth: btusb: Add support for TLV read version format and multiple Secure Boot Engines Amit K Bag
2020-04-17 9:50 ` Amit K Bag
2020-04-21 21:42 ` kbuild test robot [this message]
2020-04-22 17:45 ` [PATCH 1/2] Bluetooth: btusb: Add support for Intel Bluetooth Device Typhoon Peak (8087:0032) Marcel Holtmann
2020-04-22 17:45 ` Marcel Holtmann
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=202004220502.bdsBRSzX%lkp@intel.com \
--to=lkp@intel.com \
--cc=amit.k.bag@intel.com \
--cc=linux-firmware@kernel.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;
as well as URLs for NNTP newsgroup(s).